Methods and apparatus for processing medical data from a plurality of users

ABSTRACT

In one embodiment, a computer-implemented method that comprises receiving, a user request from a first system user of a plurality of system users for a communication of health data with a health information system. The health information system includes a data store that stores health data related to the plurality of system users. The method further comprises providing to the first system user health data stored by a second system user in the data store based on access approval by the second system user in response to a user request for health data associated with the second system user; analyzing health data for a first group of system users if the user request is an analysis of health data associated with the first group of system users; providing to the first system user the analyzed health data; and communicating health data associated with the first system user to a second group of system users if the user request is a request to communicate and the first system user has designated the system users of the second group of system users.

RELATED APPLICATION

This application is a U.S. National Phase Application under 35 USC 371of International Application PCT/US2013/072501, filed Nov. 29, 2013,which claims benefit of, and priority under 35 USC § 119(e) from U.S.provisional application No. 61/732,390, filed Dec. 2, 2012, and claimsbenefit of, and priority under 35 USC § 119(e) from U.S. provisionalapplication No. 61/750,786, filed Jan. 9, 2013, which are allincorporated by reference herein in their entirety.

This application claims benefit of, and priority under 35 USC § 119(e)from U.S. provisional application No. 61/750,786, filed Jan. 9, 2013,which is incorporated by reference herein in its entirety.

BACKGROUND

The disclosure relates to methods and systems for processing medicaldata, and in particular, to methods and systems for processing medicaldata from health care providers, payers and patients.

The healthcare system is experiencing extreme upheaval. The costs ofinsurance, medical care, and pharmaceuticals are escalating. The agingpopulation is adding a severe strain to an already burdened system.

Further, both providers and payers typically have a transactionalmindset for health care. Both providers and payers view medical care andpayment as a series of transactions, rather than a process.

Further, there is a proliferation of dedicated personal healthcaredevices, such as physical activity sensors or blood sugar meters, andsmart phones and tablets have personal healthcare applications. However,these devices provide data only to the patient, either directly from thedevice, or to the patient's healthcare application.

FIG. 1 is a block diagram illustrating data flow in a conventionalhealth data system 100. Conventional health data system 100 comprises apatient 108, a health information exchange/electronic health record(HIE/EHR) system 110, a health data source developer 112, an analyticsdeveloper 114, a hospital 120, a physician 122, a health data source127, an insurance company 128, and a government entity 129.

The data communication in the conventional health data processing system100 is via discrete communication links Patient 108 communicatesseparately with health data source developer 112, hospital 120,physician 122, health data source 127, insurance company 128 andgovernment entity 129. Hospital 120 communicates separately with HIE/EHRsystem 110, health data source developer 112, physician 122, insurancecompany 128, and government entity 129. Health data source developer 112communicates separately with physician 122 and health data source 127.Analytics developer 114 communicates with health data source developer112 and health data source 127. The numerous communication linksincreases with increasing numbers of patient 108, health data sourcedeveloper 112, analytics developer 114, hospital 120, physician 122,health data source 127, insurance company 128 and government entity 129.

It is desirable to have a system that processes medical data fromvarious sources.

SUMMARY

Embodiments of the present invention include systems and methods forprocessing medical data. In one embodiment, the present inventionincludes a computer-implemented method that comprises receiving, by acontroller, a user request from a first system user of a plurality ofsystem users for a communication of health data with a healthinformation system. The health information system includes thecontroller and a data store that stores health data related to theplurality of system users. The method further comprises providing to thefirst system user, by the controller, health data stored by a secondsystem user in the data store based on access approval by the secondsystem user in response to a user request for health data associatedwith the second system user; analyzing, by the controller, health datafor a first group of system users if the user request is an analysis ofhealth data associated with the first group of system users; providing,by the controller, to the first system user the analyzed health data;and communicating, by the controller, health data associated with thefirst system user to a second group of system users if the user requestis a request to communicate and the first system user has designated thesystem users of the second group of system users.

In another embodiment, the present invention includes a computerreadable medium embodying a computer program for performing a method andembodiments described above.

In another embodiment, the present invention includes a computer systemcomprising one or more processors implementing the techniques describedherein.

The following detailed description and accompanying drawings provide abetter understanding of the nature and advantages of the presentinvention.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating data flow in a conventionalhealth data system.

FIG. 2 is a block diagram illustrating a health data processing systemaccording to innovations herein.

FIG. 3 is a block diagram illustrating a health information processingsystem of the health data processing system of FIG. 2.

FIG. 4 is a block diagram illustrating a data store of the healthinformation processing system of FIG. 3.

FIGS. 5a and 5b illustrate a process for the health data processingsystem of FIG. 2.

FIG. 6 illustrates a screenshot for patient login in the process ofFIGS. 5a and 5 b.

FIG. 7 illustrates a screenshot for patient main menu options in theprocess of FIGS. 5a and 5 b.

FIG. 8 illustrates a screenshot for a personal data options menu of thepatient in the process of FIGS. 5a and 5 b.

FIG. 9 illustrates a screenshot for data sharing menu of the patient inthe process of FIGS. 5a and 5 b.

FIG. 10 illustrates a screenshot for a device data menu of the patientin the process of FIGS. 5a and 5 b.

FIG. 11 illustrates a screenshot for a health applications menu of thepatient in the process of FIGS. 5a and 5 b.

FIG. 12 illustrates a screenshot for a results/vitals menu of thepatient in the process of FIGS. 5a and 5 b.

FIG. 13 illustrates a screenshot for a history menu of the patient inthe process of FIGS. 5a and 5 b.

FIG. 14 illustrates a screenshot for a ranking menu of the patient inthe process of FIGS. 5a and 5 b.

FIGS. 15a and 15b illustrate a process for a provider of the health dataprocessing system of FIG. 2.

FIG. 16 illustrates a screenshot for provider login in the process ofFIGS. 15a and 15 b.

FIG. 17 illustrates a screenshot for provider main menu options in theprocess of FIGS. 15a and 15 b.

FIG. 18 illustrates a screenshot for provider data in the process ofFIGS. 15a and 15 b.

FIG. 19 illustrates a screenshot for device data accessible by aprovider in the process of FIGS. 15a and 15 b.

FIG. 20 illustrates a screenshot for health applications accessible by aprovider in the process of FIGS. 15a and 15 b.

FIG. 21 illustrates a screenshot for patient data accessible by aprovider in the process of FIGS. 15a and 15 b.

FIG. 22 illustrates a screenshot for rankings by a provider in theprocess of FIGS. 15a and 15 b.

FIG. 23 illustrates a screenshot for the health data processing systemof FIG. 2 accessible by a provider in the process FIGS. 15a and 15 b.

FIG. 24 illustrates a process for a payer of the health data processingsystem of FIG. 2.

FIG. 25 illustrates a screenshot for payer login in the process of FIG.24.

FIG. 26 illustrates a screenshot for payer main menu options in theprocess of FIG. 24.

FIG. 27 illustrates a screenshot for provider data accessible by a payerin the process of FIG. 24.

FIG. 28 illustrates a screenshot for device data accessible by a payerin the process of FIG. 24.

FIG. 29 illustrates a screenshot for health applications data accessibleby a payer in the process of FIG. 24.

FIG. 30 illustrates a screenshot for patient data accessible by a payerin the process of FIG. 24.

FIG. 31 illustrates a screenshot for the health data processing systemof FIG. 2 accessible by a payer in the process of FIG. 24.

FIGS. 32a and 32b illustrate a process for a health data sourcedeveloper of the health data processing system of FIG. 2.

FIG. 33 illustrates a screenshot for health data source developer loginin the process of FIGS. 32a and 32 b.

FIG. 34 illustrates a screenshot for health data source developer mainmenu options in the process of FIGS. 32a and 32 b.

FIG. 35 illustrates a process for an analytics developer of the healthdata processing system of FIG. 2.

FIG. 36 illustrates a screenshot for analytics developer login in theprocess of FIG. 35.

FIG. 37 illustrates a screenshot for analytics developer main menuoptions in the process of FIG. 35.

FIG. 38 illustrates a screenshot for application development by ananalytics developer in the process of FIG. 35.

FIG. 39 illustrates a process for a ranking engine of the healthinformation processing system of FIG. 3.

FIG. 40 illustrates a process for adjusting a ranking of a patient forthe process of FIG. 39.

FIG. 41 illustrates a process for adjusting a ranking of a provider forthe process of FIG. 39.

FIG. 42 illustrates a process for a ranking engine of the healthinformation processing system of FIG. 3 for ranking a new healthapplication or health data source.

FIG. 43 illustrates a process for a ranking engine of the healthinformation processing system of FIG. 3 for generating composite overallrankings for a health application or health data source.

FIG. 44 illustrates a process for generating display information forscreenshots of ranking information.

FIG. 45 illustrates a screenshot for ranking a health data source.

FIG. 46 illustrates a screenshot for ranking health applications andhealth data sources.

FIG. 47 illustrates a screenshot for health applications available to apatient in the marketplace.

FIG. 48 illustrates a screenshot for a health data source that aphysician can evaluate for recommending or prescribing to patients.

FIG. 49 illustrates a screenshot for a health data source that a patientcan evaluate for purchase.

FIG. 50 illustrates a screenshot of consolidation of health applicationsand health data sources of a patient.

FIG. 51 illustrates a screenshot of consolidated data of medications.

FIG. 52 illustrates a block diagram of associations between health datasources and one or more health applications as one embodiment of theconsolidation of FIG. 50.

FIG. 53 illustrates a block diagram of associations between healthapplications and one or more health data sources of the consolidation ofFIG. 50.

FIG. 54 illustrates a process for generating health or wellness metricsby the health data processing system of FIG. 2.

FIG. 55 illustrates hardware used to implement embodiments of the healthdata processing system of FIG. 2.

FIG. 56 illustrates a screenshot of patients of a provider in theprocess of FIGS. 15a and 15 b.

FIG. 57 illustrates a screenshot of a patient selected by a providerfrom the screenshot of FIG. 56.

FIG. 58 illustrates a screenshot of analytics of medical data of thepatient of the screenshot of FIG. 57.

FIG. 59 illustrates a screenshot of consolidated data of a health datadevice of a patient.

FIG. 60 illustrates a screenshot of improvements of employees of anemployer in the process of FIG. 24.

FIG. 61 illustrates a screenshot of discounts offered to employees of anemployer in the process of FIG. 24.

FIG. 62 illustrates a block diagram of application interfaces forapplications developers and analytics developers of the health dataprocessing system of FIG. 2.

FIGS. 63a, 63b, 63c, and 63d illustrate a process for accessing by, ahealth application developer, data of the health data processing systemof FIG. 2.

FIGS. 64a, 64b, and 64c illustrate a process for providing a softwaredevelopment kit and application programming interface by a health datasource developer of the health data processing system of FIG. 2.

DETAILED DESCRIPTION

Various embodiments of the present invention are now described withreference to the figures where like reference numbers indicate identicalor functionally similar elements. Also in the figures, the left mostdigits of each reference number corresponds to the figure in which thereference number is first used.

Reference in the specification to “one embodiment”, “an embodiment”,“various embodiments” or “some embodiments” means that a particularfeature, structure, or characteristic described in connection with theseembodiments is included in at least one embodiment of the invention, andsuch references in various places in the specification are notnecessarily all referring to the same embodiment.

Some portions of the detailed description that follows are presented interms of algorithms and symbolic representations of operations on databits within a computer memory. These algorithmic descriptions andrepresentations are the means used by those skilled in the dataprocessing arts to most effectively convey the substance of their workto others skilled in the art. An algorithm is here, and generally,conceived to be a self-consistent sequence of steps (instructions)leading to a desired result. The steps are those requiring physicalmanipulations of physical quantities. Usually, though not necessarily,these quantities take the form of electrical, magnetic or opticalsignals capable of being stored, transferred, combined, compared andotherwise manipulated. It is convenient at times, principally forreasons of common usage, to refer to these signals as bits, values,elements, symbols, characters, terms, numbers, or the like. Furthermore,it is also convenient at times, to refer to certain arrangements ofsteps requiring physical manipulations of physical quantities as modulesor code devices, without loss of generality.

However, all of these and similar terms are to be associated with theappropriate physical quantities and are merely convenient labels appliedto these quantities. Unless specifically stated otherwise as apparentfrom the following discussion, it is appreciated that throughout thedescription, discussions utilizing terms such as “processing” or“computing” or “calculating” or “determining” or “displaying” or thelike, refer to the action and processes of a computer system, or similarelectronic computing device, that manipulates and transforms datarepresented as physical (electronic) quantities within the computersystem memories or registers or other such information storage,transmission or display devices.

Certain aspects of the present invention include process steps andinstructions described herein in the form of an algorithm. It should benoted that the process steps and instructions of the present inventioncould be embodied in software, firmware or hardware, and when embodiedin software, could be downloaded to reside on and be operated fromdifferent platforms used by a variety of operating systems.

The present invention also relates to an apparatus for performing theoperations herein. This apparatus may be specially constructed for therequired purposes, or it may comprise a general-purpose computerselectively activated or reconfigured by a computer program stored inthe computer. Such a computer program may be stored in a computerreadable storage medium, such as, but is not limited to, any type ofdisk including floppy disks, optical disks, CD-ROMs, magnetic-opticaldisks, read-only memories (ROMs), random access memories (RAMs), EPROMs,EEPROMs, magnetic or optical cards, application specific integratedcircuits (ASICs), or any type of media suitable for storing electronicinstructions, and each coupled to a computer system bus. Furthermore,the computers referred to in the specification may include a singleprocessor or may be architectures employing multiple processor designsfor increased computing capability.

The algorithms and displays presented herein are not inherently relatedto any particular computer or other apparatus. Various general-purposesystems may also be used with programs in accordance with the teachingsherein, or it may prove convenient to construct more specializedapparatus to perform the required method steps. The required structurefor a variety of these systems will appear from the description below.In addition, the present invention is not described with reference toany particular programming language. It will be appreciated that avariety of programming languages may be used to implement the teachingsof the present invention as described herein, and any references belowto specific languages are provided for disclosure of enablement and bestmode of the present invention.

FIG. 2 is a block diagram illustrating a health data processing system200 according to innovations herein. Health data processing system 200comprises a plurality of system users 201 and a health informationprocessing system 202. For convenience, references to health informationprocessing system 202 are shown in some of the Figures as PatientKey™ orPatientKey™ system. PatientKey™ is a trademark of PatientKey Inc. Systemusers 201 comprises a plurality of providers 204, a plurality of payers206, a plurality of patient systems 208, a health informationexchange/electronic health record (HIE/EHR) system 210, a plurality ofhealth data source developers 212, and a plurality of analyticsdevelopers 214. For convenience, a patient using patient system 208 isalso referred to as patient 208. For simplicity and clarity, only onehealth data source developer 212 and only one analytics developer 214are shown. Also, for simplicity and clarity, only two patient systems208 are shown. Health data processing system 200 may include any numberof patient systems 208, health data source developer 212 and analyticsdeveloper 214.

Health information processing system 202 provides and facilitatescommunication, either real-time or delayed, between system users 201.For example, health information processing system 202 communicatesmedical and health monitoring data about a patient, for example,information about a patient's chronic disease, such as blood sugar for adiabetic patient, and provides the blood sugar information to providers204. In some embodiments, patient 208 enables access to the data frompatient system 108, which may include sensors of the patient. Data maybe communicated between system users 201 and health informationprocessing system 202 at times selected by the system user 201generating the data, or in some instances, by other system users 201.For example, patient 208 may control download of data to healthinformation processing system 202, and in some instances, a provider 204may control either in real-time or at a selected time the download ofdata.

Health information processing system 202 provides systems and proceduresfor various system users 201 to rank other system users 201. Ranking isdescribed further in conjunction with FIGS. 39-46.

Health information processing system 202 provides tools for processingthe data received from system users 201. Health information processingsystem 202 receives data from patient system 208, and processes the datato analytics developer 214 to develop or update the health applicationanalytics. Health information processing system 202 may process the datato assist providers 204 in providing medical care or wellness care topatient 208. Health information processing system 202 processes data forchronic disease management, general health, and athletic performance.Health information processing system 202 stores data for long-termdisease management.

Health information processing system 202 provides security forprotecting data stored in health information processing system 202 andcommunicated between health information processing system 202 and systemusers 201. Health information processing system 202 authenticates peopleor systems trying to access health information processing system 202 asauthorized system users 201. Health information processing system 202may include a telephone call center for system users 201 to communicatewith health information processing system 202.

In some embodiments, health information processing system 202 providesan open application program interface for use and development of healthdata source developers 212 and analytics developers 214.

In various embodiments, health information processing system 202 allowspatients 208 to import data from patient selected health data sources227.

In various embodiments, health information processing system 202provides data mining of data for individual patient 208, healthapplication, or health data source 227 or groups of patients 208, healthapplications, or health data sources 227.

In various embodiments, health information processing system 202provides information and services to patient 208 to take more controland responsibility for health decisions and have more information duringvisits with providers 204. Health information processing system 202provides information and recommendations to patient 208 regardingbehavior change for improved health. Health information processingsystem 202 detects patterns of data across health data sources 227 toencourage or reinforce positive behavior changes by patient 208. Healthinformation processing system 202 provides a platform for patient 208(or other system users 201) to share information, either for specifichealth applications or health data sources 227 or in bundles, withselected individuals, groups, or system users 201. The bundles may be,for example, groups of health applications, groups of health datasources 227 or groups of both health applications and health datasources 227.

Providers 204 provide medical care, services, or treatment to patient208. In some embodiments, providers 204 include a plurality of hospitals220 and a plurality of physicians 222. For simplicity and clarity, onlyone hospital 220 and only one physician 222 are shown. Providers 204 mayuse health information processing system 202 to search for health datasources 227 and health applications to prescribe to patients 208.Providers 204 may rank health data sources 227 and health applicationsusing health information processing system 202. Providers 204 may usehealth information processing system 202 to receive patient data frompatient 208 or patient data that is analyzed by health informationprocessing system 202.

Payers 206 provide approval or disapproval for medical services providedby providers 204 and provide payment for such approved medical services.In some embodiments, payers 206 comprise at least one insurance company228. In some embodiments, payers 206 comprise at least one governmententity 229, such as a Federal agency that administers Medicare. In someembodiments, payers 206 comprise at least one health care sponsor 230,such as an employer or union.

Patient system 208 communicates data about the patient to healthinformation processing system 202. In some embodiments, patient system208 includes a patient interface 226 for communicating with the patient.Patient interface 226 may includes a web browser. In some embodiments,patient system 208 includes at least one health data source 227. Forsimplicity and clarity, only two health data sources 227 are shown.Patient system 208 may download data entered by patient 208 on patientinterface 226 or downloaded from a health data source 227 to healthinformation processing system 202 with access authorization determinedby patient 208. Patient 208 may search health information processingsystem 202 for health applications or health data sources 227 forpurchase and use, research health applications or health data sources227 prescribed by provider 204 or recommended by payer 206. Patient 208may use health information processing system 202 to rank healthapplications or health data sources 227.

Health data source 227 may monitor one or more physiological parametersof one or more body systems of the patient. In some embodiments, healthdata source 227 monitors the circulatory system of the patient bymonitoring, for example, heart rate or blood pressure.

In some embodiments, health data source 227 includes applications in apersonal device of the patient, such as a smart phone, tablet, orpersonal computer.

In some embodiments, health data source 227 monitors blood chemistry,such as glucose or blood oxygen.

In some embodiments, health data source 227 provides health maintenanceto patient 208. Such health data source 227 may be, for example, anoxygen source or a continuous positive air pressure (CPAP) device.

In some embodiments, health data source 227 includes fitness, activityor wellness monitors, such as devices that monitor physical movement ofthe patient.

Health information exchange/electronic health record (HIE/EHR) system210 stores information about individual patients or populations.

Health data source developer 212 uses health information processingsystem 202 to receive data from health data sources 227 that may or maynot be analyzed by health information processing system 202 and rankingsby patients 208, providers 204 and payers 206. Health data sourcedeveloper 212 uses health information processing system 202 to publishinterface specifications for health data sources 227 for development ofhealth applications by analytics developers 214.

Analytics developer 214 uses health information processing system 202 toreceive data from health data sources 227 that may or may not beanalyzed by health information processing system 202, rankings bypatients 208, providers 204 and payers 206, and interface specificationsfor health data sources 227 from health data source developers 212 todevelop or modify health applications. Analytics developer 214 useshealth information processing system 202 to post health applications toa health application store, either operated by health informationprocessing system 202 or a third party.

In health information processing system 202 described herein, patients208 may take more control of their health. Health information processingsystem 202 provides information to patients 208 that can encourage andreinforce positive behavior changes of the patients. Health informationprocessing system 202 consolidates data from multiple health datasources 227, and may do such with more than one health application ordevice per portal. Health information processing system 202 may userbrowser, tablet or other user interfaces with which the patient isfamiliar, and process data to improved remote communication andcoordination between patients 208 and providers 204. Health informationprocessing system 202 allows patients 208 to share or bundle informationwith family and friends, and to associate with like sufferers.

In health information processing system 202 described herein, healthinformation processing system 202 may aggregate, filter, and secureactionable patient data to providers 204. This data allows providers 204to ensure improved patient adherence to treatment regimes. Healthinformation processing system 202 provides access, expansion, or maycreate a marketplace for health applications and health data sources227.

In the health information processing system 202 described herein, healthinformation processing system 202 may reduce costs for payers 206 byimproving compliance and wellness by patients 208 and optimizing carefrom nurse practitioners and other non-physician health care providers.Health information processing system 202 provides analytics on datapatients 208 whose identity is redacted so patients 208 are anonymous.

In the health information processing system 202 described herein, healthinformation processing system 202 may provide a common data platformthat allows data aggregation across health data sources 227. The accessto the marketplace by health information processing system 202 expandsawareness of health data sources 227 by other system users 201, and inparticular, patients 208, physicians 222, and analytics developers 214.

In the health information processing system 202 described herein, healthinformation processing system 202 may provide a common data platformthat allows interfacing to all data sources by analytics developers 214.The access to the marketplace by health information processing system202 expands access to health data sources 227 for analytics developers214.

In various embodiments, health information processing system 202 storesa record of each transaction, or a specified type of transactions, bysystem users 201 or types of systems users 201 with health informationprocessing system 202. Such records may be used for audits. For example,provider 204 may be a network of physicians 222 and nurses that eachaccess health information processing system 202 for a group of patients208. Health information processing system 202 records each transactionby each physician 222 and each nurse. In addition to a physician 222 ornurse being able to determine who made an early entry or change, therecords stored in health information processing system 202 may be usedto determine who accessed the records.

FIG. 3 is a block diagram illustrating health information processingsystem 202. Health information processing system 202 comprises a clientinterface 302, a security engine 304, a survey engine 306, anapplication store 308, a ranking engine 310, a data analytics engine312, a software development engine 314, a health services coordinationengine 316, a prescription engine 318, a laboratory engine 319, a userapplication engine 320, an advertising engine 322, and a data store 330.

Client interface 302 provides a communication interface between healthinformation processing system 202 and system users 201. In someembodiments, client interface 302 is an interface for communicating overthe Internet using a Transmission Control Protocol/Internet Protocol(TCP/IP).

Security engine 304 provides security for protecting data stored inhealth information processing system 202 and communicated between healthinformation processing system 202 and system users 201. Security engine304 encrypts data stored in data store 330 or communicated over clientinterface 302, such as per protocols to comply with laws and regulations(e.g., Health Insurance Portability and Accountability Act of 1996(HIPPA)). Security engine 304 authenticates people or systems trying toaccess health information processing system 202 as an authorized systemusers 201.

Survey engine 306 generates surveys of usage by system users 201.

Application store 308 generates an ecommerce source for patients 208 topurchase or download healthcare applications to their health data source127. Analytics developer 214 may also provide the healthcareapplications to health information processing system 202 for evaluationand inclusion in application store 308.

Ranking engine 310 processes rankings made by system users 201 togenerate composite rankings for the various system users 201 and anoverall composite ranking Ranking is described further in conjunctionwith FIGS. 39-46.

Data analytics engine 312 analyzes the data from system users 201 togenerate rankings, regulatory compliance, patient device usage, healthtrends, efficacy of devices, health applications, and other processingof data from patient 208, health data source 227, health application,medication, providers 204 and payer 206. Data analytics engine 312 maygroup or analyze patient data based on various parameters, including,for example, employer, geography, gender, ethnicity, age, lifestyle,lifestyle, personal data, personal health, medications, health datasources 227, health applications, system user 201 browsing history,services used by system user 201 or imported data from HIE/EHR 210.

Data analytics engine 312 analyzes the data from system users 201 todetect health trends of patients 208 to determine potential chronichealth conditions.

Software development engine 314 is used by developers to write softwarefor health information system 202.

Health services coordination engine 316 coordinates health care servicesto patients 208 based on input from hospitals 220 or physicians 222. Thehealth care services may be, for example, home health services providedby a nurse or other health service worker at the home of a patient 208.

Prescription engine 318 coordinates prescriptions made by providers 204with patients 208 and corresponding pharmacies.

Laboratory engine 319 coordinates laboratory tests prescribed or orderedby providers 204 for patients 208 at laboratories. Laboratory tests maybe, for example, blood tests, stool tests, urine test, imaging tests,radiology tests, and the like.

User application engine 320 processes requests from system users 301 andgenerates user interface information, such as screenshots on a browser.User application engine 320 allows system users 201 access to data asauthorized by other system users 201 that provide the data. Userapplication engine 320 distributes data from one system user 201 toanother system user 201 based on requests from that one system user 201.

Advertising engine 322 processes advertising and promotion on healthinformation processing system 202 by system users 201 for display on webpages. User application engine 320 processes requests from system users301 and generates user interface information, such as screenshots on abrowser.

Data store 330 stores data from system users 201 or processed by healthinformation processing system 202. Data store 330 stores data forlong-term disease management.

FIG. 4 is a block diagram illustrating data store 330. Data store 330comprises a patient data store 402, a provider data store 404, a payerdata store 406, and a HIE/EHR data store 408 for storing data receivedfrom patient systems 208, providers 204, payers 206, and HIE/EHR system210, respectively. Data store 330 further comprises a redacted patientdata store 412 for storing patient data that has patient identifiersremoved.

FIGS. 5a and 5b illustrate a process for health information processingsystem 202 for a patient 208. At 502, user application engine 320generates a user interface, such as the screenshot 600 of FIG. 6, whichis described below, for display on patient interface 226 for patient 208to login. At 504, security engine 304 authenticates the patient, and ifauthenticated, user application engine 320 generates a user interface,such as the screenshot 700 of FIG. 7, which is described below, fordisplay on patient interface 226 for patient 208 to select an action. Invarious embodiments, user application engine 320 directs patient 208 toa platform that is run by another system user 201 with which patient 208has an affiliation. For example, patient 208 may have insurance coveragethrough a particular health maintenance organization. In this case, userapplication 320 directs patient 208 to a screenshot and platform that isfor that health maintenance organization with data provided in part bythat health maintenance organization and in part by health informationprocessing system 202. This may be done between other system users 201,such as a physician 222 that is part of the health maintenanceorganization.

At 506, user application engine 320 receives a patent request frompatient 208. If, at 508, the patient selects personal data, at 510, userapplication engine 320 performs the requested action and generates auser interface of patient personal data, such as the screenshot 800 ofFIG. 8, which is described below, for display on patient interface 226for patient 208 to select an action. User application engine 320executes a patient request from the screenshot generated at 510 orreturns to waiting to receive a patient request at 506.

If, at 512, the patient selects data sharing, at 514, user applicationengine 320 performs the requested action and generates a user interfaceof patient data sharing, such as the screenshot 900 of FIG. 9, which isdescribed below, for display on patient interface 226 for patient 208 toselect an action. User application engine 320 executes a patient requestfrom the screenshot generated at 514 or returns to waiting to receive apatient request at 506.

If, at 516, the patient selects data device, at 518, user applicationengine 320 performs the requested action and generates a user interfaceof health data sources 127, such as the screenshot 1000 of FIG. 10,which is described below, for display on patient interface 226 forpatient 208 to select an action. User application engine 320 executes apatient request from the screenshot generated at 518 or returns towaiting to receive a patient request at 506.

If, at 520, the patient selects health application, at 522, userapplication engine 320 performs the requested action and generates auser interface of health applications, such as the screenshot 1100 ofFIG. 11, which is described below, for display on patient interface 226for patient 208 to select an action. User application engine 320executes a patient request from the screenshot generated at 522 orreturns to waiting to receive a patient request at 506.

If, at 524, the patient selects results/vitals, at 526, user applicationengine 320 performs the requested action and generates a user interfacefor results/vitals of health applications, health data sources 227 orboth, such as the screenshot 1200 of FIG. 12, which is described below,for display on patient interface 226 for patient 208 to select anaction. User application engine 320 executes a patient request from thescreenshot generated at 526 or returns to waiting to receive a patientrequest at 506.

If, at 528, the patient selects history, at 530, user application engine320 performs the requested action and generates a user interface forpurchase history, data share, review, or recommendations reviewed, suchas the screenshot 1300 of FIG. 13, which is described below, for displayon patient interface 226 for patient 208 to select an action. Userapplication engine 320 executes a patient request from the screenshotgenerated at 530 or returns to waiting to receive a patient request at506.

If, at 532, the patient selects ranking, at 534, user application engine320 performs the requested action and generates a user interface forranking providers 204, health data sources 227 or health applications,such as the screenshot 1400 of FIG. 14, which is described below, fordisplay on patient interface 226 for patient 208 to select an action.User application engine 320 executes a patient request from thescreenshot generated at 534 or returns to waiting to receive a patientrequest at 506.

FIG. 6 illustrates a screenshot 600 for the login of patient 208.Screenshot 600 comprises a tool bar 602, a plurality of menus 604 a and604 b, a legal information selection element 624, and a login menu 630.Toolbar 602 and menus 604 include a plurality of icons or links (notshown) for navigation, retrieving or changing information on thewebsite, For simplicity, only two menus 604 are shown, but thescreenshot may include any number of menus. A pop-up menu 620 is a menuthat appears on screenshot 600 when an icon or link in menu 604 isselected. Tool bar 602, menus 604, legal information selection element624, and login menu 630 may be located anywhere within the screenshot.In various embodiments, menu 604 b includes advertisements. In someembodiments, menu 604 b may be located along the right side or thebottom of the screenshot or both.

Tool bar 602 also includes a pull down menu 614 that may include theicons in tool bar 602, menus 604, legal information selection element624, and login menu 630. Tool bar 602 also includes a search orinstruction icon 616 for searching health information processing system202 for user accessible information. Tool bar 602 further includes amarketplace icon 617 for navigating the user to a marketplace of healthapplications, health data sources 227, or information for providers 204,payers 206, or other system users 201 depending on the context of thecurrent screenshot. Elements of tool bar 602 may be arranged anywherewithin tool bar 602.

Legal information selection element 624 allows the user to navigate to ascreen that displays legal agreements, legal disclaimers, userauthorizations, privacy disclosures, and the like.

Login menu 630 comprises a user name selection element 630 a and apassword selection element 630 b for patient 208 to enter a user nameand password, respectively. Login menu 630 further comprises a user nameor password help selection element 630 c to assist patient 208 ifpatient 208 has forgotten the user name or password.

FIG. 7 illustrates a screenshot 700 for patient main menu options inhealth information processing system 202 for patient 208. Screenshot 700comprises a tool bar 702, a plurality of menus 604 a and 604 b, a legalinformation selection element 624, and an option menu 730. Tool bar 702includes an account information icon 710 that allows the user to accessaccount information, such as payment information, for the user. Toolbar702 further includes pull down menu icon 614, search icon 616, andmarketplace icon 617. Toolbar 702 also includes a “my applications icon”717 that allows the user to access his apps/devices.

Option menu 730 comprises a personal data selection element 730 a forthe user to access, add, or modify personal data, such as personalinformation, medical history and conditions, pharmaceuticals that thepatient is or was prescribed or over the counter medications, wellness,and financial information, such as credit card or bank information forpayment for services from health information processing system 202.Selecting personal data selection element 730 a is described below inconjunction with FIG. 8.

Option menu 730 comprises a data disclosure selection element 730 b forpatient 208 to access, add, or modify data disclosure authorizations,such as sharing or bundling selected information with payers, providers,or family, sharing information anonymously with health informationprocessing system 202 for a global sharing of anonymous data with healthinformation processing system 202, providers 204, health data sourcedeveloper 212 or analytics developer 214. Data disclosure selectionelement 730 b also allows patient 208 to view comments made by thosewith whom data is shared. Data disclosure may be selective, in thatdifferent system users 201 have access to different data. In someembodiments, health information processing system 202 provides a socialmedia platform or access to a social media platform, such as Facebook,GooglePlus, or LinkedIn. Selecting data disclosure selection element 730b is described below in conjunction with FIG. 9. In some embodiments,health information processing system 202 allows patient 208 to toggle onor off data sharing.

Option menu 730 comprises a data device selection element 730 c for theuser to access, add, or modify information regarding health data source227, such device selection, controlling timing of uploading ofinformation, ranking, recommending a data device, or searching for newdata devices. Health data sources 227 that are available to a patient208 may be determined by provider 204, payer 206, or health informationprocessing system 202 based on personal data, health, wellness, or otherfactors of patient 208. Selecting data device selection element 730 c isdescribed below in conjunction with FIG. 10.

Option menu 730 comprises a health application selection element 730 dfor the user to access, add, or modify information regarding healthapplications for health data source 227, such as selection of healthdata source 227 currently used by the user or recommended by physician222, ranking, recommending a health application, or searching for newhealth applications devices. Selecting health application selectionelement 730 d is described below in conjunction with FIG. 11.

Option menu 730 comprises a health issues prioritization selectionelement 730 e for the user to access, add, or modify the user's priorityof health issues, such as medical conditions, medications, health datasources 227, or health applications for health data source 227. Invarious embodiments, advertising engine 322 generates and displaysadvertisements on the web page of patient 208 based on the priority ofhealth issues set by patient 208 using health issues prioritizationselection element 730 e.

Option menu 730 comprises a chronic health issues prioritizationselection element 730 f for the user to access, add, or modify theuser's priority of chronic health issues, such as chronic medicalconditions, chronic medications, chronic health data sources 227, orchronic health applications for chronic health data source 227. Invarious embodiments, advertising engine 322 generates and displaysadvertisements on the web page of patient 208 based on the chronichealth issues set by patient 208 using chronic health issuesprioritization selection element 730 f.

Option menu 730 comprises a ranking selection element 730 g for the userto access, add, or modify the user's ranking of data devices, healthapplications, and physicians, or review ranking history. Selectingranking selection element 730 g is described below in conjunction withFIG. 14.

Option menu 730 comprises a results/vitals selection element 730 h forthe user to access, add, or modify the user's health applications,health data sources 227 or both. Selecting results/vitals selectionelement 730 h is described below in conjunction with FIG. 12.

Option menu 730 comprises a history selection element 730 i for the userto access, add, or modify the user's purchase history, data share,review, or recommendations reviewed. Selecting history selection element730 i is described below in conjunction with FIG. 13.

FIG. 8 illustrates a screenshot 800, which may be generated in responseto selection of personal data selection element 730 a (FIG. 7), forpersonal data menu options for patient 208. Screenshot 800 comprises atool bar 702, a plurality of menus 604 a and 604 b, a legal informationselection element 624, and a personal data menu 830.

Personal data menu 830 comprises a personal data selection element 830 afor the user to access, add, or modify personal data. Personal data menu830 comprises a medical data menu selection element 830 b for patient208 to access, add, or modify patient medical data, such as medicalhistory, chronic conditions, and current health conditions. Personaldata menu 830 comprises a medications selection element 830 c forpatient 208 to access, add, or modify pharmaceuticals that patient 208is or was prescribed or over the counter medications that the patient istaking.

Personal data menu 830 comprises a wellness selection element 830 d forpatient 208 to access, add, or modify wellness data, such as theexercise regiment, diet, and stress reduction regiment of the user.Personal data menu 830 comprises a financial data selection element 830e for patient 208 to access, add, or modify financial information, suchas credit card or bank information for payment for services from healthinformation processing system 202.

FIG. 9 illustrates a screenshot 900 for patient data disclosure menu ofpatient 208, which may be generated in response to selection of datadisclosure selection element 730 b (FIG. 7). Screenshot 900 comprises atool bar 702, a plurality of menus 604 a and 604 b, a legal informationselection element 624, and a data disclosure menu 930.

Data disclosure menu 930 comprises a data sharing with payers 206selection element 930 a for patient 208 to access, add, or modify datadisclosure authorizations for sharing selected information or bundles ofinformation with payers 206. Data disclosure menu 930 comprises a datasharing with providers 204 selection element 930 b for patient 208 toaccess, add, or modify data disclosure authorizations for sharingselected information with providers 204. Patient 208 may share with aspecific physician 222, a medical provider network, a network ofphysicians 222, nurses and staff associated with the providers 204, orother providers 204 referred to or consulted by a specific provider 204(e.g., the physician of patient 208). Data disclosure menu 930 comprisesa data sharing or bundle sharing with family selection element 930 c forpatient 208 to access, add, or modify data disclosure authorizations forsharing selected information or bundles with family, friends,caregivers, conservators, lawyers, or social workers. Data disclosuremenu 930 comprises a “sharing with groups” selection element 930 d toallow patient 208 to share data or bundles with groups. The groups maybe, for example, groups that share a common disease, such as diabetes, acommon fitness goal, use the same or similar health data device 227, usethe same or similar health application, common attributes, such as age,or the like. Data disclosure menu 930 comprises a data sharing withshare anonymous data selection element 930 e for patient 208 to access,add, or modify data disclosure authorizations for patient personal andmedical data to be shared anonymously by health information processingsystem 202 with selected system users 201. In various embodiments,health information processing system 202 provides shared dataautomatically, either scheduled, periodically, or in real-time, to thosewith whom it is being shared via, for example, email, text, or websites.

FIG. 10 illustrates a screenshot 1000, which may be generated inresponse to selection of data device selection element 730 c (FIG. 7),for a device data menu of patient 208 in the process of FIGS. 5a and 5b. Screenshot 1000 comprises a tool bar 702, a plurality of menus 604 aand 604 b, a legal information selection element 624, and a patientdevice menu 1030.

Patient device menu 1030 comprises a device data selection element 1030a, a device data upload selection element 1030 b, a rank deviceselection element 1030 c, a recommend data device selection element 1030d, and a data device search selection element 1030 e. Device dataselection element 1030 a allows patient 208 to access, add, or modifyinformation regarding health data source 227 that patient 208 currentlyuses or have been prescribed by provider 204. Device data uploadselection element 1030 b allows patient 208 to access, add, or modifyinformation regarding controlling timing of uploading of information ofhealth data sources 227. In some embodiments, patient 208 may allowprovider 204 to control the uploading of information. In someembodiments, health information processing system 202 or provider 204control uploading of information. Rank device selection element 1030 callows patient 208 to access, add, or modify information regardingrankings of health data sources 227. Recommend data device selectionelement 1030 d allows patient 208 to access, add, or modify informationregarding recommending a health data source 227. Data device searchselection element 1030 e allows patient 208 to access, add, or modifyinformation regarding searching for new data devices. In response to thedata device search selection element 1030 e, user application engine 120displays a screenshot of available health data sources 227, or ascreenshot of a specific health data source 227, such as the screenshotof FIG. 49, which are described below.

FIG. 11 illustrates a screenshot 1100, which may be generated inresponse to selection of health application selection element 730 d(FIG. 7), for a health applications menu of the patient in the processof FIGS. 5a and 5b . Screenshot 1100 comprises a tool bar 702, aplurality of menus 604 a and 604 b, a legal information selectionelement 624, and a patient health applications menu 1130.

Patient health applications menu 1130 comprises a current healthapplications selection element 1130 a, a provider recommended healthapplications selection element 1130 b, a rank health applicationsselection element 1130 c, a recommend health applications selectionelement 1130 d, and a search health applications selection element 1130e. Current health applications selection element 1130 a allows patient208 to access, add, or modify information of health applicationscurrently used by patient 208. Provider recommended health applicationsselection element 1130 b allows patient 208 to access, add, or modifyinformation related to health applications recommended by a provider 204of patient 208. Rank health applications selection element 1130 c allowspatient 208 to access, add, or modify information for ranking healthapplications used by patient 208. The rankings are described inconjunction with FIGS. 39-42. Recommend health applications selectionelement 1130 d allows patient 208 to access, add, or modify informationfor recommending for health applications. Search health applicationsselection element 1130 e allows patient 208 to access, add, or modifyinformation for searching for or perusing new health applications, andadding selected health applications to patient system 208. In responseto the selection of search health applications selection element 1130 e,user application engine 120 displays a screenshot of available healthapplications, such as the screenshot of FIG. 47, which is describedbelow.

FIG. 12 illustrates a screenshot 1200, which may be generated inresponse to selection of results/vitals selection element 730 h (FIG.7), for a results/vitals menu of the patient in the process of FIGS. 5aand 5b . Screenshot 1200 comprises a tool bar 702, a plurality of menus604 a and 604 b, a legal information selection element 624, and aresults/vitals menu 1230.

Results/vitals menu 1230 comprises a health applications selectionelement 1230 a, a health data sources selection element 1230 b, and ahealth applications and health data sources selection element 1230 c toallow patient 208 to access, add, or modify information related tohealth applications, health data sources 227, and health applications,or both.

FIG. 13 illustrates a screenshot 1300, which may be generated inresponse to selection of history selection element 730 i (FIG. 7), for ahistory menu of the patient in the process of FIGS. 5a and 5b .Screenshot 1300 comprises a tool bar 702, a plurality of menus 604 a and604 b, a legal information selection element 624, and a history menu1330.

History menu 1330 comprises a purchase history selection element 1330 a,a data share selection element 1330 b, a priority history reviewselection element 1330 c, and a recommendations reviewed selectionelement 1330 d to allow patient 208 to access, add, or modifyinformation related to priority of purchase history, data share, review,or recommendations reviewed.

FIG. 14 illustrates a screenshot 1400, which may be generated inresponse to selection of ranking selection element 730 g (FIG. 7), for aranking menu of the patient in the process of FIGS. 5a and 5b .Screenshot 1400 comprises a tool bar 602, a plurality of menus 604 a and604 b, a legal information selection element 624, and a patient rankingsmenu 1430.

Patient rankings menu 1430 comprises a rank data device selectionelement 1430 a, a rank health application selection element 1430 b, anda rank physician selection element 1430 c to allow patient 208 toaccess, add, or modify information related to rankings of health datasources 227, health applications, and physicians 222 (or other providers204), respectively. Patient rankings menu 1430 further comprises areview ranking history selection element 1430 d to allow patient 208 toaccess, add, or modify information related to the history of rankings bypatient 208. Rankings are described in conjunction with FIGS. 39-46.

FIGS. 15a and 15b illustrate a process for health information processingsystem 202 for a provider 204. At 1502, user application engine 320generates a user interface, such as the screenshot 1600 of FIG. 16,which is described below, for display on an interface of provider 204for provider 204 to login. At 1504, security engine 304 authenticatesprovider 204, and if authenticated, user application engine 320generates a user interface, such as the screenshot 1700 of FIG. 17,which is described below, for display for provider 204 to select anaction.

At 1506, user application engine 320 receives a request from provider204. If, at 1508, provider 204 selects provider data, at 1510, userapplication engine 320 performs the requested action and generates auser interface of provider data, such as the screenshot 1800 of FIG. 18,which is described below, for display on an interface of provider 204for provider 204 to select an action. User application engine 320executes a provider 204 request from the screenshot generated at 1510 orreturns to waiting to receive a provider 204 request at 1506.

If, at 1512, provider 204 selects device data, at 1514, user applicationengine 320 performs the requested action and generates a user interfaceof health data sources 227, such as the screenshot 1900 of FIG. 19,which is described below, for display on an interface of provider 204for provider 204 to select an action. User application engine 320executes a provider 204 request from the screenshot generated at 1514 orreturns to waiting to receive a provider 204 request at 1506.

If, at 1516, provider 204 selects health application, at 1518, userapplication engine 320 performs the requested action and generates auser interface of health applications, such as the screenshot 2000 ofFIG. 20, which is described below, for display on an interface ofprovider 204 for provider 204 to select an action. User applicationengine 320 executes a provider 204 request from the screenshot generatedat 1518 or returns to waiting to receive a provider 204 request at 1506.

If, at 1520, provider 204 selects patient, at 1522, user applicationengine 320 performs the requested action and generates a user interfaceof patient data, such as the screenshot 2100 of FIG. 21, which isdescribed below, for display on an interface of provider 204 forprovider 204 to select an action. User application engine 320 executes aprovider 204 request from the screenshot generated at 1522 or returns towaiting to receive a provider 204 request at 1506.

If, at 1524, provider 204 selects ranking, at 1526, user applicationengine 320 performs the requested action and generates a user interfacefor ranking, such as the screenshot 2200 of FIG. 22, which is describedbelow, for display on an interface of provider 204 for provider 204 toselect an action. User application engine 320 executes a provider 204request from the screenshot generated at 1526 or returns to waiting toreceive a provider 204 request at 1506.

If, at 1528, provider 204 selects access to health informationprocessing system 202, at 1530, user application engine 320 performs therequested action and generates a user interface for access to healthinformation processing system 202, such as the screenshot 2300 of FIG.23, which is described below, for display on an interface of provider204 for provider 204 to select an action. User application engine 320executes a provider 204 request from the screenshot generated at 1530 orreturns to waiting to receive a provider 204 request at 1506.

FIG. 16 illustrates a screenshot 1600 for the login of provider 204 inthe process of FIGS. 15a and 15b . Screenshot 1600 comprises a tool bar602, a plurality of menus 604 a and 604 b, a legal information selectionelement 624, and a login menu 1630.

Login menu 1630 comprises a user name selection element 1630 a and apassword selection element 1630 b for provider 204 to enter a user nameand password, respectively. Login menu 1630 further comprises a username or password help selection element 1630 c to assist provider 204 ifprovider 204 has forgotten the user name or password.

FIG. 17 illustrates a screenshot 1700 for provider main menu options inhealth information processing system 202 for provider 204 in the processof FIGS. 15a and 15b . Screenshot 1700 comprises a tool bar 1702, aplurality of menus 604 a and 604 b, a legal information selectionelement 624, and a provider option menu 1730. Toolbar 702 includes pulldown menu icon 614, search icon 616, marketplace icon 617, and accountinformation icon 1710. Toolbar 702 also includes an analysis icon 1717that allows provider to access analysis by health information processingsystem 202. In various embodiments, selection of analysis icon 1717navigates directly to the screenshot of FIG. 23. In various embodiments,selection of analysis icon 1717 navigates directly to the screenshot ofFIG. 56.

Provider option menu 1730 comprises a provider data selection element1730 a, a data device selection element 1730 b, a health applicationsselection element 1730 c, a patient selection element 1730 d, a rankselection element 1730 e, and a health information processing system 202selection element 1730 f. Provider data selection element 1730 a allowsprovider 204 to access, add, or modify information related to provider204, composite data of patients, and set up or change accountinformation or features of health information processing system 202.Selecting provider data selection element 1730 a is described below inconjunction with FIG. 18.

Data device selection element 1730 b allows provider 204 to access, add,or modify information regarding health data sources 227, such as devicedata, device selection, or device rankings, searching for new datadevices, analysis of health data sources 227 by health informationprocessing system 202. Selecting data device selection element 1730 b isdescribed below in conjunction with FIG. 19.

Health applications selection element 1730 c allows provider 204 toaccess, add, or modify information regarding health applications, suchas health application selection, health application rankings, searchingfor new heath applications, analysis of health applications by healthinformation processing system 202. Selecting health applicationsselection element 1730 c is described below in conjunction with FIG. 20.

Patient selection element 1730 d allows provider 204 to access, add, ormodify information related to a patient 208, such as patient data orhealth data sources used by patient 208, information related toprescribing health data sources 227 or health applications to thepatient or prescribe using groups of patients, or analysis of patientdata, devices or health applications by health information processingsystem 202. Selecting patient selection element 1730 d is describedbelow in conjunction with FIG. 21.

Rank selection element 1730 e allows provider 204 to access, add, ormodify the ranking of health data sources 227, health applications,medications, treatments, or review ranking history. Selecting rankselection element 1730 e is described below in conjunction with FIG. 22.

Health information processing system 202 selection element 1730 f allowsprovider 204 to access, add, or modify the data on health informationprocessing system 202. Selecting health information processing system202 selection element 1730 f is described below in conjunction with FIG.23.

FIG. 18 illustrates a screenshot 1800, which may be generated inresponse to selection of provider data selection element 1730 a (FIG.17), for provider data in the process of FIGS. 15a and 15b . Screenshot1800 comprises a tool bar 1702, a plurality of menus 604 a and 604 b, alegal information selection element 624, and a provider data menu 1830.

Provider data menu 1830 comprises a provider selection element 1830 a, acomposite patient data selection element 1830 b, and a healthinformation processing system selection element 1830 c. Providerselection element 1830 a allows provider 204 to access, add, or modifyinformation related to provider 204. Composite patient data selectionelement 1830 b allows provider 204 to access, add, or modify informationrelated to composite data of patients. Health information processingsystem selection element 1830 c allows provider 204 to access, add, ormodify information related to account information or features of healthinformation processing system 202. The features may include, forexample, triggers for patient alerts, such as patient blood pressure.The alerts may be shown in the alerts list 5636 (FIG. 56) describedbelow.

FIG. 19 illustrates a screenshot 1900, which may be generated inresponse to selection of data device selection element 1730 b (FIG. 17),for device data accessible by provider 204 in the process of FIGS. 15aand 15b . Screenshot 1900 comprises a tool bar 1702, a plurality ofmenus 604 a and 604 b, a legal information selection element 624, and adevice data menu 1930.

Device data menu 1930 comprises a device data selection element 1930 a,a ranking selection element 1930 b, a search devices selection element1930 c, and a health information processing system 202 selection element1930 d. Device data selection element 1930 a allows provider 204 toaccess, add, or modify information related to health data sources 227.Ranking selection element 1930 b allows provider 204 to access, add, ormodify information related to ranking health data sources 227. Searchdevices selection element 1930 c allows provider 204 to search forhealth data sources 227. In response to the selection of search devicesselection element 1930 c, user application engine 120 displays ascreenshot of available health data sources 227, or a screenshot of aspecific health data source 227, such as the screenshot of FIG. 48,which are described below. Health information processing system 202selection element 1930 d allows provider 204 to access, add, or modifyinformation related to health data sources 227 that is provided byprovider 204 to health information processing system 202.

FIG. 20 illustrates a screenshot 2000, which may be generated inresponse to selection of health applications selection element 1730 c(FIG. 17), for health applications accessible by a provider in theprocess of FIGS. 15a and 15b . Screenshot 2000 comprises a tool bar1702, a plurality of menus 604 a and 604 b, a legal informationselection element 624, and a provider health applications menu 2030.

Provider health applications menu 2030 comprises a health applicationsselection element 2030 a, a ranking selection element 2030 b, a searchhealth applications selection element 2030 c, and a health informationprocessing system 202 selection element 2030 d. Health applicationsselection element 2030 a allows provider 204 to access, add, or modifyinformation related to health applications. Ranking selection element2030 b allows provider 204 to access, add, or modify information relatedto ranking health applications. Search health applications selectionelement 2030 c allows provider 204 to access, add, or modify informationrelated to search for health applications. Health information processingsystem 202 selection element 2030 d allows provider 204 to access, add,or modify information related to health applications that is provided byprovider 204 to health information processing system 202.

FIG. 21 illustrates a screenshot 2100, which may be generated inresponse to selection of patient selection element 1730 d (FIG. 17), forpatient data accessible by a provider in the process of FIGS. 15a and15b . Screenshot 2100 comprises a tool bar 1702, a plurality of menus604 a and 604 b, a legal information selection element 624, and apatient data menu 2130.

Patient data menu 2130 comprises a patient data selection element 2130a, a patient devices selection element 2130 b, a health applicationselection element 2130 c, a patient prescribing selection element 2130d, a group based prescribing selection element 2130 e, and a healthinformation processing system 202 selection element 2130 f. Patient dataselection element 2130 a allows provider 204 to access, add, or modifyinformation related to patient data. In response to the selection ofpatient data selection element 2130 a, health information processingsystem 202 may display the screenshot of FIG. 56. Patient devicesselection element 2130 b allows provider 204 to access, add, or modifyinformation related to health data sources 227 that are used by patients208 of provider 204. Health application selection element 2130 c allowsprovider 204 to access, add, or modify information related to healthapplications that are used by patients 208 of provider 204. Patientprescribing selection element 2130 d allows provider 204 to access, add,or modify information related to prescribing health data sources 227 orhealth applications or bundles thereof to patient 208. Prescriptions ofhealth applications or health data sources 227 or bundles thereof may bemade automatically based on criteria set by provider 204 or manual byprovider 204. Group based prescribing selection element 2130 e allowsprovider 204 to access, add, or modify information related toprescribing health data sources 227 or health applications or bundlesthereof using groups of patients 208, or analysis of patient data,devices or health applications by health information processing system202. Health information processing system 202 selection element 2130 fallows provider 204 to access, add, or modify information related toanalysis of patient data that is provided by provider 204 to healthinformation processing system 202.

FIG. 22 illustrates a screenshot 2200, which may be generated inresponse to selection of rank selection element 1730 e (FIG. 17), forrankings by a provider in the process of FIGS. 15a and 15b . Screenshot2200 comprises a tool bar 1702, a plurality of menus 604 a and 604 b, alegal information selection element 624, and a ranking menu 2230.

Ranking menu 2230 comprises a rank data device selection element 2230 a,a rank health application selection element 2230 b, a review rankinghistory selection element 2230 c, and a provider ranking selectionelement 2230 d. Rank data device selection element 2230 a allowsprovider 204 to access, add, or modify information related to rankingsof health data sources 227. Rank health application selection element2230 b allows provider 204 to access, add, or modify information relatedto rankings of health applications. Review ranking history selectionelement 2230 c allows provider 204 to access, add, or modify informationrelated to the history of rankings by provider 204. Rankings aredescribed in conjunction with FIGS. 39-46. Provider ranking selectionelement 2230 d allows provider 204 to access, add, or modify informationrelated to rankings of provider 204 by patients 208 of provider 204.

FIG. 23 illustrates a screenshot 2300, which may be generated inresponse to selection of health information processing system 202selection element 1730 f (FIG. 17), for the health data processingsystem of FIG. 2 accessible by a provider in the process FIGS. 15a and15b . Screenshot 2300 comprises a tool bar 1702, a plurality of menus604 a and 604 b, a legal information selection element 624, and a healthinformation processing system 202 menu 2330.

Health information processing system 202 menu 2330 comprises a payersselection element 2330 a, a data device selection element 2330 b, ahealth application selection element 2330 c, a patient selection element2330 d, a ranking selection element 2330 e, and an upload selectionelement 2330 f. Payers selection element 2330 a allows provider 204 toaccess, add, or modify information related to payers 206. Data deviceselection element 2330 b allows provider 204 to access, add, or modifyinformation related to health data sources 227 used by patients 208 ofprovider 204 or on the market or in development. Health applicationselection element 2330 c allows provider 204 to access, add, or modifyinformation related to health applications used by patients 208 ofprovider 204 or on the market or in development. Patient selectionelement 2330 d allows provider 204 to access, add, or modify informationrelated to patents 208 of provider 204. The information is informationthat patent 108 has authorized provider 204 to access (see FIG. 9).Ranking selection element 2330 e allows provider 204 to access, add, ormodify information related to rankings by provider 204 (see FIG. 22) orotherwise provided by health information processing system 202. Uploadselection element 2330 f allows provider 204 to upload new or modifiedinformation from provider 204 to health information processing system202. Health information processing system 202 may provide analysis toproviders 204, such as the number of patients 208 that are using ahealth application or health data source 227 recommended by theprovider, improvement in health of patients 208 who are using aparticular health application or health data source 227, comparison inhealth improvement of patients 208 who are using a health application orhealth data source 227 and others who are not using any healthapplication or health data source 227, what their patients are sayingabout them, and the like.

FIGS. 24a and 24b illustrate a process for health information processingsystem 202 for a payer 206. At 2402, user application engine 320generates a user interface, such as the screenshot 2500 of FIG. 25,which is described below, for display on an interface of payer 206 forpayer 206 to login. At 2404, security engine 304 authenticates payer206, and if authenticated, user application engine 320 generates a userinterface, such as the screenshot 2600 of FIG. 26 or a screenshot 6000of FIG. 60, which are described below, for display for payer 206 toselect an action.

At 2406, user application engine 320 receives a request from payer 206.If, at 2408, payer 206 selects provider data, at 2410, user applicationengine 320 performs the requested action and generates a user interfaceof provider data, such as the screenshot 2700 of FIG. 27, which isdescribed below, for display on an interface of payer 206 for payer 206to select an action. User application engine 320 executes a payer 206request from the screenshot generated at 2410 or returns to waiting toreceive a payer 206 request at 2406.

If, at 2412, payer 206 selects device data, at 2414, user applicationengine 320 performs the requested action and generates a user interfaceof health data sources 227, such as the screenshot 2800 of FIG. 28,which is described below, for display on an interface of payer 206 forpayer 206 to select an action. User application engine 320 executes apayer 206 request from the screenshot generated at 2414 or returns towaiting to receive a payer 206 request at 2406.

If, at 2416, payer 206 selects health application, at 2418, userapplication engine 320 performs the requested action and generates auser interface of health applications, such as the screenshot 2900 ofFIG. 29, which is described below, for display on an interface of payer206 for payer 206 to select an action. User application engine 320executes a payer 206 request from the screenshot generated at 2418 orreturns to waiting to receive a payer 206 request at 2406.

If, at 2420, payer 206 selects patient, at 2422, user application engine320 performs the requested action and generates a user interface ofpatient data, such as the screenshot 3000 of FIG. 30, which is describedbelow, for display on an interface of payer 206 for payer 206 to selectan action. User application engine 320 executes a payer 206 request fromthe screenshot generated at 2422 or returns to waiting to receive apayer 206 request at 2406.

If, at 2428, payer 206 selects access to health information processingsystem 202, at 2430, user application engine 320 performs the requestedaction and generates a user interface for access to health informationprocessing system 202, such as the screenshot 3100 of FIG. 31, which isdescribed below, for display on an interface of payer 206 for payer 206to select an action. User application engine 320 executes a payer 206request from the screenshot generated at 2430 or returns to waiting toreceive a payer 206 request at 2406.

FIG. 25 illustrates a screenshot 2500 for the login of payer 206 in theprocess of FIG. 24. Screenshot 2500 comprises a tool bar 602, aplurality of menus 604 a and 604 b, a legal information selectionelement 624, and a login menu 2530.

Login menu 2530 comprises a user name selection element 2530 a and apassword selection element 2530 b for payer 206 to enter a user name andpassword, respectively. Login menu 2530 further comprises a user name orpassword help selection element 2530 c to assist payer 206 if payer 206has forgotten the user name or password.

FIG. 26 illustrates a screenshot 2600 for payer main menu options inhealth information processing system 202 for payer 206. Screenshot 2600comprises a tool bar 1702, a plurality of menus 604 a and 604 b, a legalinformation selection element 624, and a payer option menu 2630.

Payer option menu 2630 comprises a provider data selection element 2630a, a data device selection element 2630 b, a health applicationsselection element 2630 c, a patient selection element 2630 d, and ahealth information processing system 202 selection element 2630 e.Provider data selection element 2630 a allows payer 206 to access, add,or modify information related to payer 206, composite data of patients,and set up or change account information or features of healthinformation processing system 202. Selecting provider data selectionelement 2630 a is described below in conjunction with FIG. 27.

Data device selection element 2630 b allows payer 206 to access, add, ormodify information regarding health data sources 227, such as devicedata, health applications for health data sources 227, or devicerankings, or analysis of health data sources 227 by health informationprocessing system 202. Selecting data device selection element 2630 b isdescribed below in conjunction with FIG. 28.

Health applications selection element 2630 c allows payer 206 to access,add, or modify information regarding health applications, or healthapplication rankings, or analysis of health applications by healthinformation processing system 202. Selecting health applicationsselection element 2630 c is described below in conjunction with FIG. 29.

Patient selection element 2630 d allows payer 206 to access, add, ormodify information related to a patient 208, such as patient data orhealth data sources used by patient 208, information related toprescribed health data sources 227, health applications to the patient,or medications, or analysis of provider data, patient data, devices orhealth applications by health information processing system 202.Selecting patient selection element 2630 d is described below inconjunction with FIG. 30.

Health information processing system 202 selection element 2630 f allowspayer 206 to access, add, or modify data on health informationprocessing system 202, such as finances, efficacy, trends, provider orpatient data, or upload data to health information processing system202. Selecting health information processing system 202 selectionelement 2630 f is described below in conjunction with FIG. 31.

FIG. 27 illustrates a screenshot 2700, which may be generated inresponse to selection of provider data selection element 2630 a (FIG.26), for provider data accessible by payer 206 in the process of FIG.24. Screenshot 2700 comprises a tool bar 1702, a plurality of menus 604a and 604 b, a legal information selection element 624, and a providerdata menu 2730.

Provider data menu 2730 comprises a provider selection element 2730 a, aprovider ranking by patient data selection element 2730 b, and a healthinformation processing system 202 selection element 2730 c. Providerselection element 2730 a allows payer 206 to access, add, or modifyinformation related to provider 204. Provider ranking by patient dataselection element 2730 b allows payer 206 to access, add, or modifyinformation related to rankings of providers 204 that are made bypatients 208. Health information processing system 202 selection element2730 c allows payer 206 to access, add, or modify analysis of providers204 by health information processing system 202.

FIG. 28 illustrates a screenshot 2800, which may be generated inresponse to selection of data device selection element 2630 b (FIG. 28),for device data accessible by payer 206 in the process of FIG. 24.Screenshot 2800 comprises a tool bar 1702, a plurality of menus 604 aand 604 b, a legal information selection element 624, and a device datamenu 2830.

Device data menu 2830 comprises a device data selection element 2830 a,a ranking selection element 2830 b, and a health information processingsystem 202 selection element 2830 c. Device data selection element 2830a allows payer 206 to access, add, or modify information related tohealth data sources 227. Ranking selection element 2830 b allows payer206 to access, add, or modify information related to ranking health datasources 227. Health information processing system 202 selection element2830 c allows payer 206 to access, add, or modify information related tohealth data sources 227 that is provided by payer 206 to healthinformation processing system 202.

FIG. 29 illustrates a screenshot 2900, which may be generated inresponse to selection of health applications selection element 2630 c(FIG. 26), for health applications data accessible by payer 206 in theprocess of FIG. 24. Screenshot 2900 comprises a tool bar 1702, aplurality of menus 604 a and 604 b, a legal information selectionelement 624, and a payer health applications menu 2930.

Payer health applications menu 2930 comprises a health applicationsselection element 2930 a, a ranking selection element 2930 b, and ahealth information processing system 202 selection element 2930 c.Health applications selection element 2930 a allows payer 206 to access,add, or modify information related to health applications. Rankingselection element 2930 b allows payer 206 to access, add, or modifyinformation related to ranking health applications. Health informationprocessing system 202 selection element 2930 d allows payer 206 toaccess, add, or modify information related to health applications thatis provided by payer 206 to health information processing system 202.

FIG. 30 illustrates a screenshot 3000, which may be generated inresponse to selection of patient selection element 2630 d (FIG. 26), forpatient data accessible by a payer 206 in the process of FIG. 24.Screenshot 3000 comprises a tool bar 1702, a plurality of menus 604 aand 604 b, a legal information selection element 624, and a patient datamenu 3030.

Patient data menu 3030 comprises a patient data selection element 3030a, a patient devices selection element 3030 b, a patient prescribedselection element 3030 c, and a health information processing system 202selection element 3030 e. Patient data selection element 3030 a allowspayer 206 to access, add, or modify information related to patient data.Patient devices selection element 3030 b allows payer 206 to access,add, or modify information related to health data sources 227 that areused by patients 208 that are to be paid by payer 206. Patientprescribed selection element 3030 c allows payer 206 to access, add, ormodify information related to prescribed health data sources 227 orhealth applications to the patient. Health information processing system202 selection element 3030 d allows payer 206 to access, add, or modifyinformation related to analysis of patient data that is provided bypayer 206 to health information processing system 202.

FIG. 31 illustrates a screenshot 3100, which may be generated inresponse to selection of health information processing system 202selection element 2630 f (FIG. 26), for the health data processingsystem of FIG. 2 accessible by payer 206 in the process of FIG. 24.Screenshot 3100 comprises a tool bar 1702, a plurality of menus 604 aand 604 b, a legal information selection element 624, and a healthinformation processing system 202 menu 3130.

Health information processing system 202 menu 3130 comprises a financesselection element 3130 a, an efficacy selection element 3130 b, a trendsselection element 3130 c, a patient/provider selection element 3130 d,and an upload data selection element 3130 e. Finances selection element3130 a allows payer 206 to access, add, or modify information related topatients 208, providers 204, or payers 206. Efficacy selection element3130 b allows payer 206 to access, add, or modify information relatedefficacy of medications, health care, or treatment that is determined indata from other system users 201 by health information processing system202. Trends selection element 3130 c allows payer 206 to access, add, ormodify information related to trends determined in data from othersystem users 201 by health information processing system 202.Patient/provider selection element 3130 d allows payer 206 to access,add, or modify information related to patents 208 or providers 204. Theinformation is information that patient 208 has authorized payer 206 toaccess (see FIG. 9). Upload data selection element 3130 e allows payer206 to upload information related to payer 206 to health informationprocessing system 202. Health information processing system 202 mayprovide analysis to payers 206, such as the number of patients 208 thatare using a health application or health data source 227 recommended bythe payer, improvement in health of patients 208 who are using aparticular health application or health data source 227, comparison inhealth improvement of patients 208 who are using a health application orhealth data source 227 and others who are not using any healthapplication or health data source 227, what their patients are sayingabout them, and the like.

FIGS. 32a and 32b illustrate a process for health information processingsystem 202 for health data source developer 212. In various embodiments,health information processing system 202 provides a platform for healthdata source developers 212 to develop health data sources 227 andanalytics developers 214 to develop health applications. In someembodiments, health data source developers 212 publish softwaredevelopment kits, application program interfaces, and interfacespecifications for their data in health information processing system202. In some embodiments, health information processing system 202 has astandard or protocol for software development kits, application programinterfaces, and interface specifications.

At 3202, user application engine 320 generates a user interface, such asthe screenshot 3300 of FIG. 33, which is described below, for display onan interface of health data source developer 212 for health data sourcedeveloper 212 to login. At 3204, security engine 304 authenticateshealth data source developer 212, and if authenticated, user applicationengine 320 generates a user interface, such as the screenshot 3400 ofFIG. 34, which is described below, for display for health data sourcedeveloper 212 to select an action.

At 3206, user application engine 320 receives a request from health datasource developer 212. If, at 3208, health data source developer 212selects access to health information processing system 202, at 3210,user application engine 320 performs the requested action and generatesa user interface of data of health information processing system 202,such as a screenshot that is similar to screenshot 3100 (FIG. 31), fordisplay on an interface of health data source developer 212 for healthdata source developer 212 to select an action. User application engine320 executes a health data source developer 212 request from thescreenshot generated at 3210 or returns to waiting to receive a healthdata source developer 212 request at 3206.

If, at 3212, health data source developer 212 selects analyticsdeveloper, at 3214, user application engine 320 performs the requestedaction and generates information from analytics developers 114 fordisplay on a user interface of health data sources 227 for display on aninterface of health data source developer 212 for health data sourcedeveloper 212 to select an action. Health information processing system202 may provide analysis to health data source developer 212 as to theeffectiveness of their applications or devices, such as the number ofpatients 208 that are using a health application or health data source227, comparison in health improvement patients 208 who are using aparticular health application or health data source 227, comparison inhealth improvement of patients 208 who are using a health application orhealth data source 227 and others who are not using any healthapplication or health data source 227, what their patients are sayingabout them, and the like. User application engine 320 executes a healthdata source developer 212 request from the screenshot generated at 3214or returns to waiting to receive a health data source developer 212request at 3206.

If, at 3216, health data source developer 212 selects health datasources analysis, at 3218, user application engine 320 performs therequested action and generates a user interface of information foranalyzing health data sources 227, such as troubleshooting a defectiveproduct or simulation of design changes based on data from healthinformation processing system 202, for display on an interface of healthdata source developer 212 for health data source developer 212 to selectan action. User application engine 320 executes a health data sourcedeveloper 212 request from the screenshot generated at 3218 or returnsto waiting to receive a health data source developer 212 request at3206.

If, at 3220, health data source developer 212 selects device data, at3222, user application engine 320 performs the requested action andgenerates a user interface of device data for display on an interface ofhealth data source developer 212 for health data source developer 212 toselect an action, such as view or download device data. User applicationengine 320 executes a device data request from the screenshot generatedat 3222 or returns to waiting to receive a health data source developer212 request at 3206.

If, at 3224 health data source developer 212 selects ranking, at 3226,user application engine 320 performs the requested action and generatesa user interface that displays ranking information and patient commentson health data sources 227 on an interface of health data sourcedeveloper 212 for health data source developer 212 to select an action.User application engine 320 executes a health data source developer 212request from the screenshot generated at 3226 or returns to waiting toreceive a health data source developer 212 request at 3206.

If, at 3228, health data source developer 212 selects approval requestto health information processing system 202, at 3230, user applicationengine 320 performs the requested action and generates a user interfacefor access to health information processing system 202 with an approvalrequest of a new or modified health data source 227 for display on aninterface of health data source developer 212 for health data sourcedeveloper 212 to select an action. User application engine 320 executesa health data source developer 212 request from the screenshot generatedat 3230 or returns to waiting to receive a health data source developer212 request at 3206.

FIG. 33 illustrates a screenshot 3300 for the login of health datasource developer 212 in the process of FIG. 24. Screenshot 3300comprises a tool bar 602, a plurality of menus 604 a and 604 b, a legalinformation selection element 624, and a login menu 3330.

Login menu 3330 comprises a user name selection element 3330 a and apassword selection element 3330 b for health data source developer 212to enter a user name and password, respectively. Login menu 3330 furthercomprises a user name or password help selection element 3330 c toassist health data source developer 212 if health data source developer212 has forgotten the user name or password.

FIG. 34 illustrates a screenshot 3400 for health data source developermain menu options in the process of FIGS. 32a and 32b . Screenshot 3400comprises a tool bar 1702, a plurality of menus 604 a and 604 b, a legalinformation selection element 624, and a health data source developermenu 3430.

Health data source developer menu 3430 comprises a health informationprocessing system 202 selection element 3430 a, an analytics developerdata selection element 3430 b, a “view rankings and comments” selectionelement 3430 c, a device data selection element 3430 d, an interfacespecification selection element 3430 e, and a information processingsystem 202 approval selection element 3430 f. Health informationprocessing system 202 selection element 3430 a allows health data sourcedeveloper 212 to access, add, or modify information related to dataexchanged with or analysis by health information processing system 202.Analytics developer data selection element 3430 b allows health datasource developers 212 to access, add, or modify information related toanalytics developers 214 that are generating health applications forhealth data sources 227 of health data source developer 212. “Viewrankings and comments” selection element 3430 c allows health datasource developer 212 to access, add, or modify information related torankings and comments by other system users 201. Device data selectionelement 3430 d allows health data source developer 212 to access, add,or modify information related to health data sources 227 for whichhealth data source developer 212 is writing or planning to write healthapplications. Interface specification selection element 3430 e allowshealth data source developer 212 to access, add, or modify informationrelated to uploading an interface specification for analytics developers214 to write health applications for health data sources 227 of healthdata source developer 212 or obtain regulatory approval of the healthdata source 227. In response to the selection interface specificationselection element 3430 e, health information processing system 202 mayexecute the process of FIGS. 64a, 64b, and 64c , which is describedbelow. Information processing system 202 approval selection element 3430f allows health data source developer 212 to access, add, or modifyinformation related to requests by health data source developer 212 forapproval of a new or modified health data source 227 by healthinformation processing system 202.

FIG. 35 illustrates a process for health information processing system202 for analytics developer 214. At 3502, user application engine 320generates a user interface, such as the screenshot 3600 of FIG. 36,which is described below, for display on an interface of analyticsdeveloper 214 for analytics developer 214 to login. At 3504, securityengine 304 authenticates analytics developer 214, and if authenticated,user application engine 320 generates a user interface, such as thescreenshot 3700 of FIG. 37, which is described below, for display foranalytics developer 214 to select an action.

At 3506, user application engine 320 receives a request from analyticsdeveloper 214. The analytics developer 214 may, for example, want datarelated to patient age, body mass index, disease, vitals, allergies,medications, and the like. If, at 3508, analytics developer 214 selectsaccess to health information processing system 202, at 3510, userapplication engine 350 performs the requested action and generates auser interface of data of health information processing system 202, suchas a screenshot that is similar to screenshot 3100 (FIG. 31), fordisplay on an interface of analytics developer 214 for analyticsdeveloper 214 to select an action. User application engine 320 executesan analytics developer 214 request from the screenshot generated at 3510or returns to waiting to receive an analytics developer 214 request at3506.

If, at 3512, analytics developer 214 selects analytics developer, at3514, user application engine 320 performs the requested action andgenerates information from analytics developers 114 for display on auser interface of health data sources 227 for display on an interface ofanalytics developer 214 for analytics developer 214 to select an action.User application engine 350 executes an analytics developer 214 requestfrom the screenshot generated at 3514 or returns to waiting to receivean analytics developer 214 request at 3506.

If, at 3516, analytics developer 214 selects device data, at 3518, userapplication engine 350 performs the requested action and generates auser interface of data of health data source 227 for display on aninterface of analytics developer 214 for analytics developer 214 toselect an action. User application engine 320 executes an analyticsdeveloper 214 request from the screenshot generated at 3518 or returnsto waiting to receive an analytics developer 214 request at 3506.

If, at 3520, analytics developer 214 selects interface publication, at3522, user application engine 350 performs the requested action andgenerates a user interface for publication of interface specification ofthe health application for display on an interface of analyticsdeveloper 214 for analytics developer 214 to select an action, such asview or download the interface specification. User application engine320 executes a device data request from the screenshot generated at 3522or returns to waiting to receive an analytics developer 214 request at3506.

If, at 3528, analytics developer 214 selects approval request to healthinformation processing system 202, at 3530, user application engine 320performs the requested action and generates a user interface for accessto health information processing system 202 with an approval request ofa new or modified health application for display on an interface ofanalytics developer 214 for analytics developer 214 to select an action.User application engine 350 executes an analytics developer 214 requestfrom the screenshot generated at 3530 or returns to waiting to receivean analytics developer 214 request at 3506.

FIG. 36 illustrates a screenshot 3600 for the login of analyticsdeveloper 214 in the process of FIG. 24. Screenshot 3600 comprises atool bar 602, a plurality of menus 604 a and 604 b, a legal informationselection element 624, and a login menu 3630.

Login menu 3630 comprises a user name selection element 3630 a and apassword selection element 3630 b for analytics developer 214 to enter auser name and password, respectively. Login menu 3630 further comprisesa user name or password help selection element 3630 c to assistanalytics developer 214 if analytics developer 214 has forgotten theuser name or password.

FIG. 37 illustrates a screenshot 3700 for analytics developer main menuoptions for analytics developer 214 in the process of FIG. 35.Screenshot 3700 comprises a tool bar 1702, a plurality of menus 604 aand 604 b, a legal information selection element 624, and an analyticsdeveloper main menu 3700.

Analytics developer main menu 3700 comprises a health informationprocessing system 202 selection element 3730 a, a patient data selectionelement 3730 b, a third party review selection element 3730 c, an APIinformation selection element 3730 d, and an application store selectionelement 3730 e. Health information processing system 202 selectionelement 3730 a allows analytics developer 214 to access, add, or modifyinformation related to data exchanged with or analysis by healthinformation processing system 202. Patient data selection element 3730 ballows analytics developer 214 to access, add, or modify informationrelated to patient data that patient 208 has authorized to be sharedwith analytics developer 214 or grouped data processed or analyzed byhealth information processing system 202. Third party review selectionelement 3730 c allows analytics developer 214 to access, add, or modifyinformation related to third party review of health applications. Thirdparties may be, for example, regulatory agencies or testing andvalidation entities. An API information selection element 3730 d allowsanalytics developer 214 to access, add, or modify information andinstructions related to application programming interface (API)instructions and information of health information processing system 202for health application development by analytics developer 214. Selectingapplication data selection element 3730 d is described below inconjunction with FIG. 38. Application store selection element 3730 eallows analytics developer 214 to access, add, or modify informationrelated to an application store that may be an ecommerce websiteoperated by analytics developer 214 or a third party. Selection ofapplication store selection element 3730 e allows analytics developer214 to place a new or modified health application for availability fordownload by patient 208, remove or alter health applications that arecurrently available, or post announcements on the health applicationstore.

FIG. 38 illustrates a screenshot 3800, which may be generated inresponse to selection of application data selection element 3730 d (FIG.37), for application development by analytics developer 214 in theprocess of FIG. 35. Screenshot 3800 comprises a tool bar 1702, aplurality of menus 604 a and 604 b, a legal information selectionelement 624, and an application development menu 3830.

Application development menu 3830 comprises an analytics softwareselection element 3830 a, a patient data analysis selection element 3830b, a provider data analysis selection element 3830 c, a simulationengine selection element 3830 d, an information processing system 202approval selection element 3830 e, a data device library interfaceselection element 3830 f, and a health information processing system 202platform selection element 3830 g. Analytics software selection element3830 a allows analytics developer 214 to access, add, modify, or analyzeinformation related to analytics software that analytics developers 214has or is developing for health applications for health data sources227. Patient data selection element 3830 b allows analytics developer214 to access, add, or modify information related to patient 208 relatedto health applications of analytics developer 214 for which patient 208has authorized access by analytics developer 214. Provider data analysisselection element 3830 c allows analytics developer 214 to access, addmodify, or analyze information related to provider 204 related to healthapplications of analytics developer 214 for which provider 204 hasauthorized access by analytics developer 214. Simulation engine sselection element 3830 d allows analytics developer 214 to access, add,or modify information related to a simulation engine that tests andevaluates health applications under development or developed byanalytics developer 214 using data from health information processingsystem 202. Information processing system 202 approval selection element3830 e allows analytics developer 214 to access, add, or modifyinformation related to requests by analytics developer 214 for approvalof a new or modified health application by health information processingsystem 202. Data device library interface selection element 3830 fallows analytics developer 214 to access, add, or modify informationrelated to an interface for a library of the data device. Healthinformation processing system 202 platform selection element 3830 gallows analytics developer 214 to access, add, or modify informationrelated to a platform API and environment for health informationprocessing system 202.

FIG. 39 illustrates a process for ranking engine 310. At 3902, rankingengine 310 receives a patient ranking for a provider 204, a healthapplication, or a health data source 227, such as provided at 534 (FIG.5) or a selection from screenshot 1400 (FIG. 14). At 3904, rankingengine 310 receives a provider ranking for a health application or ahealth data source 227, such as provided at 1526 (FIG. 15) or aselection from screenshot 2200 (FIG. 22). At 3906, ranking engine 310receives a payer ranking for a health application or a health datasource 227, such as provided from a selection from screenshot 2800 (FIG.28). At 3908, ranking engine 310 determines whether the ranking frompatient 208, provider 204, or payer 206 is to be limited. The limitationmay be based on usage of a health application or health data source 227,other medical conditions of patient 208, If the ranking is to be limitedat 3908, ranking engine 310, at 3910, executes the process of FIG. 40for patient 208 or the process of FIG. 41 for provider 204 or payer 206.

If the ranking is not limited at 3908 or after the ranking has beenlimited at 3910, ranking engine 310 at 3916, determines a compositeranking based on the ranking of patient 208, provider 204, and payer206. At 3918, ranking engine 310 provides the composite overall ranking,composite patent ranking, composite physician ranking and compositepayer rankings to patient 208, payer 206 and provider 204.

FIG. 40 illustrates a process for adjusting a ranking of patient 208 forthe process of FIG. 39. At 4002, ranking engine 310 receives patientdata from data store 330. At 4004, ranking engine 310 receives patientdevice data from data store 330. At 4006, ranking engine 310 analyzesthe patient data and patient device data to determine whether rankingsshould be adjusted or limited. At 4008, ranking engine 310 adjusts thepatient ranking based on various factors, such as device usage, patientmedical history, patient past history of rankings, and other patientrankings Δt 4010, ranking engine 310 determines a weight of the patientranking for use in the composite overall ranking and overall patientranking. At 4012, ranking engine 310 returns to block 3910 of FIG. 39.

FIG. 41 illustrates a process for adjusting a ranking of provider 204 orpayer 206 for the process of FIG. 39. Although the process of FIG. 41applies for both provider 204 or payer 206, the process will bedescribed only for provider 204. At 4102, ranking engine 310 receivesprovider data from data store 330. At 4104, ranking engine 310 receivesproviders analysis of patients and devices from data store 330 At 4106,ranking engine 310 analyzes the provider data and provider analysis todetermine whether rankings should be adjusted or limited. At 4108,ranking engine 310 adjusts the provider ranking based on variousfactors, such as device prescriptions, and other provider rankings. At4110, ranking engine 310 determines a weight of the provider ranking foruse in the composite overall ranking and overall provider ranking. At4112, ranking engine 310 returns to block 3910 of FIG. 39.

FIG. 42 illustrates a process for processing rankings for a new healthapplication or health data source 227 by ranking engine 310. At 4202,ranking engine 310 determines a threshold or thresholds for the numberor numbers of system users 201 before ranking engine 310 generates acomposite ranking or displays rankings of system users 201. For example,the threshold may be a number X of patients 208 that must rank a newhealth application or health data source 227 before ranking engine 310generates a composite ranking of the new health application or healthdata source 227 by patients 208. Further, the threshold may be a numberY of physicians 222 that must rank a new health application or healthdata source 227 before ranking engine 310 generates a composite rankingof the new health application or health data source 227 by physicians222. Yet further, both the threshold X of patients 208 and the thresholdY of physicians 222 must be met before ranking engine 310 generates acomposite ranking of the new health application or health data source227. For the sake of illustration, the process of FIG. 42 is describedfor a patient 208, but the process applies for other system users 201.

In various embodiments, patient 208 is provided with an incentive to useand evaluate a new health application or health data source 227. Forexample, the incentive may be that patient 208 gets a free subscriptionor license to use the new health application or health data source 227for a limited time (e.g., six months), if patient 208 ranks the newhealth application or health data source 227 before the expiration ofthe limited time (e.g., before four months). At 4204, patient 208receives a free subscription or license to use the new healthapplication or health data source 227. At 4208, ranking engine 310determines whether a patient ranking is received, such as provided at534 (FIG. 5) within the ranking term. If the ranking is not receivedwithin the ranking term at 4208, ranking engine 310 terminates, at 4210,the free subscription of patient 208.

If the ranking is received within the ranking term at 4208, rankingengine 310 check, at 4212, the usage of the new health application orhealth data source 227 by the patient 208. If the usage is sufficient,ranking engine 310 accepts, at 4214, the patient ranking and stores theranking in ranking data 410. The evaluation of the usage by patient 208determines whether patient 208 is a regular user of the new healthapplication or health data source 227 to avoid fake rankings by familyor friends. In some embodiments, ranking engine 310 may allow patient208 a limited number (e.g., one) opportunity to submit a ranking forevaluation. In some embodiments, ranking engine 310 may terminate thesubscription if the ranking is rejected.

FIG. 43 illustrates a process for generating composite overall rankingsfor a health application or health data source 227 by ranking engine310.

At 4302, ranking engine 310 receives a patient ranking from patient 208for a health application or a health data source 227, such as providedat 534 (FIG. 5) or a selection from screenshot 1400 (FIG. 14). At 4304,ranking engine 310 generates and provides a questionnaire to patient 208for patient 208 to provide a rationale for the ranking, and receivesanswers from patient 208.

At 4306, ranking engine 310 receives a provider ranking from provider204 for a health application or a health data source 227, such asprovided at 1526 (FIG. 15) or a selection from screenshot 2200 (FIG.22). At 4308, ranking engine 310 generates and provides a questionnaireto provider 204 for provider 204 to provide a rationale for the ranking,and receives answers from provider 204.

At 4310, ranking engine 310 generates a composite patient ranking fromrankings from patients 208, a composite provider ranking from rankingsfrom providers 204, and an overall composite ranking from rankings frompatients 208 and rankings from providers 204.

At 4312, ranking engine 310 generates a system overall ranking (referredto as “PKP ranking” in FIG. 45, described below) from the patientranking at 4302, the questionnaire at 4304, the provider ranking at4306, the questionnaire at 4308.

FIG. 44 illustrates a process for generating display information forscreenshots of ranking information. The process of FIG. 44 is describedin conjunction with the screenshot of FIG. 45, which illustrates ascreenshot for rankings of a health data source 227. As an illustrativeexample, a health data source 227 is described. The display informationfor a ranking may be included in any screenshot that shows the healthapplication or health data source 227 corresponding to the ranking.

At 4402, ranking engine 310 generates an icon or popup that includes thename of a provider 204 that has ranked a health application or healthdata source 227, and may include a link to a profile of that provider204, if the provider 204 has ranked the health data source 227 above athreshold (e.g., four stars in a five star ranking system, with fivestars being highest). One such example is link 4502 (FIG. 45) for “Dr.Amy James” who gave a five star ranking to health data source 227.

At 4404, ranking engine 310 generates an icon to indicate that healthdata source 227 is approved by an entity. For example, health datasource 227 may be approved by the Food and Drug Administration (FDA).One such example is icon 4504 (FIG. 45) for an FDA icon.

At 4406, ranking engine 310 may generate an expansion or pop up windowto expand on the rankings that are displayed. For example, the rankingsmay be the composite patient ranking from rankings from patients 208,the composite provider ranking from rankings from providers 204, andthat overall composite ranking from rankings from patients 208 andrankings from providers 204 generated at 4310 (FIG. 43). The expansionmay also provide quantitative information about the rankings, such asnumber of patients 208 providing rankings and number of providers 204providing rankings. The quantitative information may be displayed withthe ranking information. One such example is expansion 4506 (FIG. 45)that shows that 1,135 patients 208 and 3 providers 204 ranked thedevice.

At 4408, ranking engine 310 adjusts the color of the ranking indicators.For example, if a number N of patients 208 ranked an application is morethan a threshold “A1”, ranking engine 310 sets the ranking stars to be acolor C1. If the number N is more than the threshold A1, but less than asecond threshold “A2”, ranking engine 310 sets the ranking stars to be acolor C2. If the number N is more than the threshold A2, ranking engine310 sets the ranking stars to be a color C3.

FIG. 46 illustrates a screenshot for ranking health applications andhealth data sources 227 of patient 208. FIG. 46 is an illustrativeembodiment of the screenshot of FIG. 14. The screenshot includes aregion 4602 that displays all or the top health applications and healthdata sources 227 that patient 208 has. The screenshot also includes aregion 4604 that displays the health applications and health datasources 227 that patient 208 has not ranked. The region 4604 may alsoinclude a time indication left for new health applications and healthdata sources 227 that have free subscriptions that impose a time limit,such as those described above in conjunction with FIG. 42. Thescreenshot also includes a region 4606 that displays health applicationsand health data sources 227 that are “hot,” such as most popular,recently reviewed in the media, trade journals, or by tradeassociations, recently approved by a regulatory agency or insurancecompany, positive trend in rankings, or the like. The screenshot furtherincludes a region 4608 that displays advertising for health applicationsand health data sources 227.

FIG. 47 illustrates a screenshot for health applications available topatient 208 in the marketplace. The screenshot of FIG. 47 may bedisplayed in response to the selection of the marketplace icon in FIGS.6-14 by patient 208 or selection of search health applications selectionelement 1130 e (FIG. 11). The screenshot may display health applicationsbased on health data sources 227 that patient 208 has, are prescribed orrecommended by physician 222, determined as being of interest based onsearches by patient 208, In various embodiments, the screenshot includeshealth applications arranged by health categories. The screenshotincludes a region 4702, a region 4704, and a region 4706 that displayhealth applications for wellness, blood glucose, and blood pressure,respectively.

FIG. 48 illustrates a screenshot for a health data source 227 thatphysician 222 can evaluate for recommending or prescribing patients 208.The screenshot of FIG. 48 may be displayed in response to the selectionof the marketplace icon in FIGS. 16-23 by physician 222 or otherprovider 204 or selection of search devices selection element 1930 c(FIG. 19). As an illustrative example, the screenshot shows a glucosedevice with descriptive text and technical specifications.

FIG. 49 illustrates a screenshot for a health data source 227 thatpatient 208 can evaluate for purchase. The screenshot of FIG. 49 may bedisplayed in response to the selection of the marketplace icon in FIGS.6-14 by patient 208, data device search selection element 1030 e (FIG.10), or a selection element of FIG. 47. As an illustrative example, thescreenshot shows a glucose device with descriptive text and technicalspecifications.

FIG. 50 illustrates a screenshot of consolidation of health applicationsand health data sources 227 of patient 208. The screenshot of FIG. 50may be displayed, for example, in response to the selection ofresults/vitals selection element 730 h (FIG. 7) or one of the resultsselection elements 1230 (FIG. 12). The screenshot includes a pluralityof health applications 5002 that patient 208 has. As an illustrativeexample, patient 208 has one wellness health application 5002, two bloodglucose health applications 5002, and one blood pressure healthapplication 5002. The screenshot also includes a plurality of healthdata sources 227 that patient 208 has. As an illustrative example,patient 208 has two wellness health data sources 227, one blood glucosehealth data source 227, and one blood pressure health data source 227.

Links 5006 connect health applications 5002 to associated health datasources 227. One health application 5002 may be connected to one or morehealth data sources 227 by one or more links 5006. A fitness healthapplication is linked to two wellness devices and a blood glucose meter.Associations are described more generally below in conjunctions withFIG. 52. One health data source 227 may be connected to one or morehealth applications 5007 by one or more links 5006. Associations aredescribed more generally below in conjunctions with FIG. 53. By linkinghealth applications and health data sources 227, patient 208 mayconsolidate health data so that the patient may display data fromrelated or linked devices and health applications, such as wellness datafrom fitness devices and blood glucose devices. Similarly, blood glucoseinformation may be displayed with exercise, diet, and blood glucosedevice measurements. The links 5006 may be displayed with visiblevariations to indicate characteristics or correlations between healthapplications 5002, health data sources 227 and characteristics ofpatients, such as patient's usage or adherence, or refresh rate,synchronization rate and the like of the health applications with healthinformation processing system 202. The visible variations may be, forexample, different colors of lines, different types of lines (such asdotted lines), different line thickness, and different line density.Another example of consolidated data is shown in FIG. 51

FIG. 51 illustrates a screenshot 5100 of consolidated data formedications. Screenshot 5100 may be displayed, for example, in responseto the selection of results/vitals selection element 730 h (FIG. 7) orone of the results selection elements 1230 (FIG. 12). Screenshot 5100illustrates the reading of a health data source 227, such as a pillbox,that detects when patient 208 takes medication. In an illustrativeexample, screenshot 5100 shows that patient 208 takes two medications,namely Coreg and Sulfonylureas, the compliance with the medicationstimes for the past two days, and a compliance rate. Screenshot 5100 alsoconsolidates data from a health data source 227 that detects cardioactivity and displays associated data.

FIG. 52 illustrates a block diagram of associations between health datasources 227 and one or more health applications. In an illustrativeembodiment, health data sources 227 are labeled D1 through D4, andhealth applications are labeled A1 through A6. Device D1 is linked tomultiple health applications, namely applications A1 and A2. Likewise,device D1 is linked to multiple health applications, namely applicationsA2 and A3, and device D4 is linked to multiple health applications,namely applications A5 and A6. However, device D3 is linked to a singlehealth application, namely application A4. Links 5206 between, healthdata sources 227 (labeled D1 through D4), and health applications(labeled A1 through A6) may be displayed with visible variations in asimilar manner as links 5006 described above.

FIG. 53 illustrates a block diagram of associations between healthapplications and one or more health data sources 277. In an illustrativeembodiment, health data sources 227 are labeled D1 through D4, andhealth applications are labeled A1 through A6. Application A1 is linkedto a single device, namely D1. Application A2 is linked to multipledevices, namely D1 and D2. Application A3 is linked to a single device,namely DD. Application A4 is linked to a single device, namely D3.Application A5 is linked to a single device, namely D4. Application A6is linked to a single device, namely D4. Links 5306 between, health datasources 227 (labeled D1 through D4), and health applications (labeled A1through A6) may be displayed with visible variations in a similar manneras links 5006 described above.

FIG. 54 illustrates a process for generating health or wellness metricsby health information processing system 202. At 5402, ranking engine 310retrieves patient data from data store 330. At 5404, ranking engine 310retrieves patient device data from data store 330. At 5406, rankingengine 310 analyzes the retrieved data, and generates, at 5408, healthand wellness metrics for patient 208. At 5410, user application engine320 provides the metrics to patient 208 and approved recipients. Dataanalytics engine 312 may analyze the metrics to determine whetherpatient 208 has indication or has a chronic condition. For example, dataanalytics engine 312 may monitor blood sugar level on a first healthdata source 227 of patient 208, and may determine that patient 208 hasindications of diabetes. Data analytics engine 312 may also monitorweight of patient 208 from a second health data source 227 of patient208, and based on an analysis of both blood sugar and weight, determinethat patient 208 is showing signs of diabetes.

FIG. 55 illustrates hardware used to implement embodiments of healthdata processing system 200. An example computer system 5510 isillustrated in FIG. 55. Computer system 5510 includes a bus 5505 orother communication mechanism for communicating information, and one ormore processors 5501 coupled with bus 5505 for processing information.Computer system 5510 also includes a memory 5502 coupled to bus 5505 forstoring information and instructions to be executed by processor 5501,including information and instructions for performing the techniquesdescribed above, for example. This memory may also be used for storingvariables or other intermediate information during execution ofinstructions to be executed by processor 5501. Possible implementationsof this memory may be, but are not limited to, random access memory(RAM), read only memory (ROM), or both. A machine readable storagedevice 5503 is also provided for storing information and instructions.Common forms of storage devices include, for example, a non-transitoryelectromagnetic medium such as a hard drive, a magnetic disk, an opticaldisk, a CD-ROM, a DVD, Blu-Ray, a flash memory, a USB memory card, orany other medium from which a computer can read. Storage device 5503 mayinclude source code, binary code, or software files for performing thetechniques above, for example. Storage device 5503 and memory 5502 areboth examples of computer readable mediums.

Computer system 5510 may be coupled via bus 5505 to a display 5512, suchas a cathode ray tube (CRT), plasma display, light emitting diode (LED)display, LED-backlit multi-touch display with in-plane switching (IPS)technology, or liquid crystal display (LCD), for displaying informationto a computer user. An input device 5511 such as a keyboard, mouseand/or touch screen is coupled to bus 5505 for communicating informationand command selections from the user to processor 5501. The combinationof these components allows the user to communicate with the system, andmay include, for example, user interface 105. In some systems, bus 5505may be divided into multiple specialized buses. Each system user 201interfaces with an input device 5511 and a display 5512.

Computer system 5510 also includes a network interface 5504 coupled withbus 5505. Network interface 5504 may provide two-way data communicationbetween computer system 5510 and the local network 5520, for example.The network interface 5504 may be a wireless network interface, a cablemodem, a digital subscriber line (DSL) or a modem to provide datacommunication connection over a telephone line, for example. Anotherexample of the network interface is a local area network (LAN) card toprovide a data communication connection to a compatible LAN. Wirelesslinks are another example. In any such implementation, network interface5504 sends and receives electrical, electromagnetic, or optical signalsthat carry digital data streams representing various types ofinformation.

Computer system 5510 can send and receive information, includingmessages or other interface actions, through the network interface 5504across a local network 5520, an Intranet, or the Internet 5530. For alocal network, computer system 5510 may communicate with a plurality ofother computer machines, such as server 5515. Accordingly, computersystem 5510 and server computer systems represented by server 5515 maybe programmed with processes described herein. In the Internet example,software components or services may reside on multiple differentcomputer systems 5510 or servers 5533-5535 across the network. Some orall of the processes described above may be implemented on one or moreservers, for example. Specifically, health data processing system 200 orelements thereof might be located on different computer systems 5510 orone or more servers 5515 and 5533-5535, for example. A server 5533 maytransmit actions or messages from one component, through Internet 5530,local network 5520, and network interface 5504 to a component oncomputer system 5510. The software components and processes describedabove may be implemented on any computer system and send and/or receiveinformation across a network, for example.

FIG. 56 illustrates a screenshot 5600 of patients 208 of physician 222.Screenshot 5600 may be displayed, for example, in response to theselection of analysis icon 1717 (FIGS. 17-23) or patient data selectionelement 2130 a (FIG. 21). Screenshot 5600 comprises a “patients” icon5602, a marketplace icon 5604, an account information icon 5606, and alog out icon 5608. The term “icon” is used interchangeably herein withthe term “selection element.”

Patients icon 5602 allows provider 204 to access, add, or modifyinformation related to patients 208 of provider 204. Screenshot 5600includes a priority list 5632 listing patients 208 that are in a first(or highest or top) priority level of medical care, such as patients 208that are in emergency, in an ambulance or hospitalized. Screenshot 5600further includes a watch list 5634 listing patients 208 that are in asecond priority level of medical care, such as patients 208 thatprovider 204 monitors at some frequency. Screenshot 5600 furtherincludes an alert list 5636 listing any patient 208 having results fromhealth care device 227, health application, medical test, or medicalevaluation that falls outside of a normal or patient-specific range.Screenshot 5600 further includes an others list 5638 that includes allpatients 208 of provider 204 that are not any of lists 5632, 5634 or5636. Selection of a patient 208, e.g., by clicking on the name orselecting a box and selecting, opens a screenshot associated with thatpatient 208. For example, in response to selecting a patient, healthinformation processing system 202 may display the screenshot of FIG. 57described below. Lists 5632, 5634, 5636, 5638 may include name, status(which may be changed from priority, watch, alert and other), adherence,next appointment (or last appointment with provider 204), andresults/vitals of patient 208.

Marketplace icon 5604 allows provider 204 to access, add, or modifyinformation related to the available health care devices 227 and healthcare applications including the ranking and number of users 201. Invarious embodiments, marketplace icon 5604 is similar to marketplaceicon 617.

Account information icon 5606 allows provider 204 to access, add, ormodify account information such as password, contact information (suchas email address, physical address, or phone number) or user name. Invarious embodiments, account information icon 5606 is similar to accountinformation selection element 710. Log out icon 5608 allows provider 204to logout of health information processing system 202.

Screenshot 5600 further comprises a results/vitals icon 5612, a providerdata icon 5614, a device data icon 5616, a health applications icon5618, a prescriptions icon 5620, a rankings icon 5622, and an analyticsicon 5624.

In response to selection of results/vitals icon 5612, health informationprocessing system 202 generates a screenshot for provider 204 thatdisplays a snapshot or summary of data from health data devices 227 andhealth applications of a patient 208 of provider 204. The screenshot maybe, for example, the screenshot or a subset of the screenshot generatedin response to selection of results/vitals selection element 730 h, ormay include further information generated by health informationprocessing system 202.

Provider data icon 5614 allows provider 204 to access, add, or modifyinformation related to provider data, such as provider name, contactinformation, specialty, medical group, and the like, for provider 204.

Device data icon 5616 allows provider 204 to access, add, or modifyinformation related to health care devices 227 recommended by provider204 and used by patients 208 of provider 204, rankings, number of users,analysis by health information processing system 202 of the health caredevices 227, and a search icon for provider 204 to search availablehealth care devices 227 for a specific medical condition. The analysisby health information processing system 202 may provide overalleffectiveness of health care device 227 and patient satisfaction withhealth care device 227. In various embodiments, device data icon 5616 issimilar to data device selection element 1730 b. In various embodiments,health information processing system 202 generates screenshot 1900 inresponse to selection of device data icon 5616.

Health applications icon 5618 allows provider 204 to access, add, ormodify information related to health applications recommended byprovider 204 and used by patients 208 of provider 204, rankings, numberof users, analysis by health information processing system 202 of thehealth applications, and a search icon for provider 204 to searchavailable health applications for a specific medical condition. Theanalysis by health information processing system 202 may provide overalleffectiveness of health applications and patient satisfaction withhealth applications. In various embodiments, health applications icon5618 is similar to health applications selection element 1730 c. Invarious embodiments, health information processing system 202 generatesscreenshot 2000 in response to selection of health applications icon5618.

Prescriptions icon 5620 allows provider 204 to access, add, or modifyinformation related to prescribing health data sources 227 or healthapplications or bundles thereof to a particular patient 208 or groups ofpatients 208. In various embodiments, provider 204 recommends healthdata sources 227 or health applications or bundles thereof to aparticular patient 208 or groups of patients 208 via email, shortmessage service (SMS) text, phone call or the like based on patientprofile (age, gender) or medical vitals (e.g., body mass index or bloodpressure) or a specific medical condition.

Health information processing system 202 may provide a future patient208 of this provider 204 with recommendations based on patient profiles,medical vitals, or specific medical condition in response to the futurepatient 208 connecting or linking to the provider 204.

In various embodiments, selection of prescriptions icon 5620 providessimilar information in screenshots as selection of patient prescribingselection element 2130 d and group based prescribing selection element2130 e.

Rankings icon 5622 allows provider 204 to access, add, or modifyinformation related to ranking of health care devices 227, healthapplications, review health ranking history, or provider ranking bypatients 208 of provider 204. In some embodiments, rankings icon 5622 issimilar to rank selection element 1730 e (FIG. 17). In variousembodiments, health information processing system 202 displaysscreenshot 2200 (FIG. 22) in response to selection of rankings icon5622.

Analytics icon 5624 allows provider 204 to access, add, or modifyinformation related to analysis performed by health informationprocessing system 202 that is accessible by provider 204. In variousembodiments, provider 204 may compare patients 208, health data devices227, and health applications based on various factors, such as resultsfor same patient from different health applications or health datadevices 227, adherence, or number of users. In various embodiments, theanalytics are displayed pictorially in pie charts, bar charts, linecharts, and the like.

In various embodiments, health information processing system 202generates analytics of vitals or improvements or changes in vitals ofpatients 208 of provider 204. For example, health information processingsystem 202 may generate the screenshot of FIG. 58 to show improvementsin vitals of a selected patient 208. In some embodiments, the vitals aredisplayed in bar charts to show the health applications used by patients208 for each vital. Each chart shows a vital with each bar indicating ahealth application.

In various embodiments, health information processing system 202generates analytics of patients 208 For example, health informationprocessing system 202 generates analytics and corresponding charts ofnumbers of patients 208 of provider 204 that are part of system 202 andusing health applications relative to patients of other providers 204.In response to a selection of a chart element, health informationprocessing system 202 may list or chart all patients (e.g., by name) ingroups based on attributes (e.g., age ranges and body mass index).

In various embodiments, health information processing system 202generates analytics of health applications or health data source 227 orbundles thereof. For example, health information processing system 202generates analytics and corresponding charts of health applications orhealth data sources 227 or bundles thereof recommended by system users201 that are logged in and adherence by patients 208 and correspondingimprovements or changes in vitals of patients of provider 204.

FIG. 57 illustrates a screenshot 5700 of a patient 208 selected byprovider 204 from screenshot 5600. Screenshot 5700 comprisesresults/vitals icon 5612, provider data icon 5614, device data icon5616, health applications icon 5618, prescriptions icon 5620, rankingsicon 5622, and analytics icon 5624. In the illustrative example shown inFIG. 57, provider 204 has selected prescriptions icon 5620. In thisillustrative example, provider 204 is prescribing a diabetes bundleincluding fitness devices and health applications, blood glucose deviceand health applications and blood pressure monitoring device. Otherpatients of the provider 204 use these devices and health applications.In this illustrative example of screenshot 5700, the displayed healthapplications and health data sources 227, which are ranked (a five starPKP ranking), of the physician 222 are displayed. A discount is shown bythe employer of the associated patient. Discounts are described inconjunction with FIG. 61.

FIG. 58 illustrates a screenshot 5800 of analytics of medical data ofthe patient of the screenshot 5700. Health information processing system202 displays, in screenshot 5800, vitals and adherence data of patient208. Provider 204 can select the vitals and the time periods to viewshort and long-term usage of health care devices 227, healthapplications, or bundles, and determine whether patient 208 understandsthe prescribed health care devices 227, health applications, or bundles,and assess whether compliance and commitment of patient 208 to treatmentand regiment for improving or maintaining health.

FIG. 59 illustrates a screenshot 5900 of consolidated data of healthdata device 227 of patient 208. Screenshot 5900 may be displayed, forexample, in response to the selection of “my applications icon” 717(FIGS. 7-14), results/vitals selection element 730 h (FIG. 7), or, ifpatient 208 has authorized access by provider 204, patient dataselection element 2130 a (FIG. 21). Screenshot 5900 comprises a “myapps” icon 5902, a marketplace icon 5904, an account information icon5906, and a log out icon 5908. “My apps” icon 5902 allows patient 208 toaccess, add, or modify information related to health data devices 227and health applications of patient 208. Marketplace icon 5904 allowspatient 208 to access, add, or modify information related to theavailable health care devices 227 and health care applications includingthe ranking and number of users 201. In various embodiments, marketplaceicon 5904 is similar to marketplace icon 617. Account information icon5906 allows patient 208 to access, add, or modify account informationsuch as password, contact information (such as email address, physicaladdress, or phone number) or user name. In various embodiments, accountinformation icon 5906 is similar to account information selectionelement 710. Log out icon 5908 allows patient 208 to logout of healthinformation processing system 202.

Screenshot 5900 further comprises a results/vitals icon 5912, a personaldata icon 5914, a data sharing icon 5916, a device data icon 5918, ahealth applications icon 5920, a rankings icon 5922, and a history icon5924.

In response to selection of results/vitals icon 5912, health informationprocessing system 202 generates a screenshot for patient that displays asnapshot or summary of data from health data devices 227 and healthapplications of patient 208. Screenshot 5900 includes may be, forexample, the screenshot or a subset of the screenshot generated inresponse to selection of results/vitals selection element 730 h, or mayinclude further information generated by health information processingsystem 202. In some embodiments, screenshot 5100 (FIG. 51) may bedisplayed instead of screenshot 5900.

Personal data icon 5914 allows patient 208 to access, add, or modifyinformation related to patient data, such as patient name, contactinformation, health information and the like, for patient 208.

Data sharing icon 5916 allows patient 208 to access, add, or modifyinformation related to sharing data with providers 204, family, friends,caregivers, conservators, lawyers, or social workers, or groups. Invarious embodiments, data sharing icon 5916 is similar to of datadisclosure selection element 730 b (FIG. 7).

Device data icon 5918 allows patient 208 to access, add, or modifyinformation related to health care devices 227 used by patients 208,recommended for use by provider 204, rankings, number of users, analysisby health information processing system 202 of health care devices 227,and a search icon for patients 208 to search available health caredevices 227 for a specific medical condition. The analysis by healthinformation processing system 202 may provide overall effectiveness ofhealth care device 227 and patient satisfaction with health care device227. In various embodiments, device data icon 5918 is similar to datadevice selection element 730 c (FIG. 7). In various embodiments, healthinformation processing system 202 generates screenshot 1000 in responseto selection of device data icon 5918.

Health applications icon 5920 allows patient 208 to access, add, ormodify information related to health applications recommended byprovider 204 and used by patients 208 of provider 204, rankings, numberof users, analysis by health information processing system 202 of thehealth applications, and a search icon for patient 208 to searchavailable health applications for a specific medical condition. Theanalysis by health information processing system 202 may provide overalleffectiveness of health applications and patient satisfaction withhealth applications. In various embodiments, health applications icon5920 is similar to health applications selection element 730 d (FIG. 7).In various embodiments, health information processing system 202generates screenshot 1100 in response to selection of healthapplications icon 5920.

Rankings icon 5922 allows patient 208 to access, add, or modifyinformation related to ranking of health care devices 227, healthapplications, or providers 204, and review health ranking history. Insome embodiments, rankings icon 5922 is similar to rank selectionelement 730 g (FIG. 7). In various embodiments, health informationprocessing system 202 displays screenshot 1400 (FIG. 14) in response toselection of rankings icon 5922.

FIG. 60 illustrates a screenshot 6000 of health care sponsor 230 that isan employer. Screenshot 6000 may be displayed, for example, at 2404(FIG. 24) for health care sponsor 230 that is an employer. Forsimplicity and clarity, health care sponsor 230 is referred to asemployer 230 herein in conjunction with FIGS. 60 and 61. Screenshot 6000comprises marketplace icon 5604, account information icon 5606, log outicon 5608, a discount icon 6012, an improvement icon 6014, and anemployee stats icon 6016.

Discount icon 6012 allows employer 230 to access, add, or modifyinformation related to discounts offered to employees on health datadevices 227, health applications, or bundles thereof. In someembodiments, health information processing system 202 analyzes data ofemployees and determines medical conditions or health conditions thatwarrant improvement and determines recommendations of health datadevices 227, health applications, or bundles thereof. Employer 230 mayoffer discounts to employees based on the recommendations. In someembodiments, health information processing system 202 generatesscreenshots, such as bar graphs, of numbers of employees having healthconditions (e.g., high blood pressure (9027), body mass index-BMI>30(16,245), high blood sugar (4,923), sick day (2109), and sport Injury(2,591)). Below the bar graph, health information processing system 202lists medical conditions that should be fixed and recommended healthapplications with overall (PKP) ranking and discount offered by employer230 to employees. In some embodiments, the discount is visible inscreenshot 6000 only to employees of employer 230.

Improvement icon 6014 allows employer 230 to access, add, or modifyinformation related to changes or improvements in employee's health.Screenshot 6000 shows an illustrative example of health of employees ofemployer 230 while improvement icon 6014 is selected. Screenshot 6000displays changes in employees' health over a selected period (1 month, 3months, 6 months, 12 months, date range) as well as variable period orduring special time period (e.g., Thanks giving and Christmas).

Screenshot 6000 further comprises a user icon 6022, a category icon6024, and a time period icon 6026. User icon 6022 allows employer 230 toaccess, add, or modify information related to types of users of healthinformation processing system 202 that are employees of employer 230.The users may be, for example, all users, executives, managers, oremployees.

Category icon 6024 allows employer 230 to access, add, or modifyinformation related to types of medical condition, vitals, healthcondition, or status of user. The categories may be, for example,medical condition, body mass index, blood pressure, blood glucose, sportinjury, or sick day (off day).

Time period icon 6026 allows employer 230 to access, add, or modifyinformation related to the time period for which the data is analyzed.The time period may be, for example, distribution over time, all day,top quarter, top half, or selected top percent, or selected time period(e.g., 1 month, 3 month, 6 month, 12 month, or user selected timeperiod).

Upon selection of icons 6022, 6024 and 6026, health informationprocessing system 202 displays the data. For example, a graph isdisplayed with average (e.g., black color graph) with improvements inone color (e.g., green) and declines in another color (e.g., red). Thegraph may also include numbers of employees. The graphs may includeinformation about health data devices 227 and health applications thatare being used and the improvements or changes in users of such devicesand applications.

Employee stats icon 6016 allows employer 6001 to access, add, or modifyinformation related to employee statistics. Employee statistics mayinclude, for example, information on when employees joined healthinformation processing system 202 or how many joined during specifictime periods (e.g., last week, last month or last three months), andnumbers of employees that synchronize data of their health data devices227 and health applications.

FIG. 61 illustrates a screenshot 6100 of employer 230 in response toselection of discount icon 6012. Screenshot 6100 comprises marketplaceicon 5604, account information icon 5606, log out icon 5608, discounticon 6012, improvement icon 6014, and employee stats icon 6016.Screenshot 6100 shows an illustrative example of discounts uponselection of discount icon 6012. Screenshot 6100 further comprises anemployee icon 6122, a category icon 6124, and an order ranking 6126.

Employee icon 6122 allows employer 230 to access, add, or modifyinformation related to types of users of health information processingsystem 202 that are employees of employer 230 for which discounts willbe offered to employees. The users may be, for example, all users,executives, managers, or employees. Category icon 6124 allows employer230 to access, add, or modify information related to types of healthdata devices 227, health applications, or bundles thereof for whichdiscounts will be offered to employees. Order ranking icon 6126 allowsemployer 230 to access, add, or modify information related to an orderhealth data devices 227, health applications, or bundles thereof will bedisplayed. The order may be, for example, based on overall (e.g., PKP)ranking, patient ranking, provider ranking, price, priority of healthissues, and the like.

FIG. 62 illustrates a block diagram of application interfaces forapplications developers 212 and analytics developers 214. Data store 330stores data from data sources 227 a, 227 b, through 227 n. As describedabove, patients 208 authorize the access of data stored in data store330 to other system users 201 based on type of system user 201 as wellas specific system user 201. Health information processing system 202generates a software development kit (SDK) and application programminginterface (API) for reading and writing information into data store 330.

Health data source developer 212 generates a SDK/API for health datasource 227 and publishes them on health information processing system202. Analytics developers 214 retrieve the SDK/API for generating healthapplications, and retrieve the data of patients 208 to generate thehealth applications. Applications developers 212 and analyticsdevelopers 214 determine the fields of data that are to be read, writtenor updated.

An application programming interface may be in hierarchical andobject-oriented programming languages and use sophisticated programminglanguage constructs. The API may include data mining functionality. TheAPI may include a mining object repository maintaining data miningmetadata, a plurality of mining project objects with each mining projectobject including data mining objects created and used by a user 201 anda plurality of mining session objects. A mining session object mayinclude data mining processing performed on behalf of a user 201 and aplurality of data mining tables.

FIGS. 63a, 63b, 63c, and 63d illustrate a process for accessing by, ahealth application developer 212, data of the health data processingsystem 200. Software development engine 314 provides an interfacethrough client interface 302 to health data source developers 212 andanalytics developers 214 to access health information processing system202 for reading and writing information in data store 330 and softwaredevelopment engine 314 for developing software.

In various embodiments, health data source developers 212 and analyticsdevelopers 214 can access information stored in data store 330 by usinga set of APIs. First, health data source developers 212 and analyticsdevelopers 214 pass their credentials to create a secure connection tosoftware development engine 314. Health data source developers 212 andanalytics developers 214 can choose the fields they want to read orupdate.

At 6302, security engine 304 authenticates the developer's applicationand checks the developer's membership status. If, at 6304, thecredentials are not valid, at 6306, security engine 304 rejects theattempt to access software development engine 314. If, at 6304, thecredentials are valid, at 6308, security engine 304 checks forpermissions that are granted to the developer by the user of the healthapplication.

If, at 6310, permissions are not granted by patient 208 or the user toaccess their records in data store 330, at 6312, security engine 304denies access to patient data. If, at 6310, permission is granted bypatient 208 or the user to access their records in data store 330, at6314, security engine 304 allows access to the associated data in datastore 330, such as by generating an access token that the developer usesto access and update data store 330.

If, at 6316, an access token had not been created, at 6318, securityengine 304 indicates that an access token was not created. In someembodiments, security engine 304 provides a help screen or a request forthe developer to reattempt to create an access token. If, at 6316, anaccess token had been created, at 6320, security engine 304 allows thedeveloper to access data store 330 and the health related data generatedby system users 201. In some embodiments, data is redacted so that thedeveloper cannot access certain information such as user name,identifiers, such as social security number or complete contactinformation. In some embodiments, the developers cannot modify any ofthe user information.

At 6322, security engine 304 allows the developer to access the user'sdata that the developer had previously generated by his application.Further, security engine 304 allows the developer to add or update thedata. At 6324, security engine 304 allows a developer to access, but notmodify, the data developed by another developer. For example, ananalytics developer 214 can access, but cannot modify, the datagenerated by a health data source developer 212.

FIGS. 64a, 64b, and 64c illustrate a process for providing a softwaredevelopment kit (SDK) and application programming interface (API) by ahealth data source developer 212. The process of FIGS. 64a, 64b, and 64cmay be in response to selection of interface specification selectionelement 3430 e (FIG. 34). At 6402, health information processing system202 provides a user interface for health data source developer 212 toregister with health information processing system 202 by providingcompany information and contact information (address, email, and supportline number) for contact by users of their SDK/API. At 6404, healthinformation processing system 202 receives upload of softwaredevelopment kit and application programming interface from health datasource developer 212 for use by analytics developers 214. At 6406,health information processing system 202 receives information fromhealth data source developer 212 for describing how others can accessdata from health data source developer 212. The information may bereceived via a form.

At 6408, health information processing system 202 approves theapplication programming interface and other documents from health datasource developer 212. At 6410, health information processing system 202provides access to the approved SDK/API for download by analyticsdevelopers 214. At 6412, software development engine 314 developsapplications using the SDK/API in response to input from analyticsdevelopers 214.

At 6414, health information processing system 202 receives applicationsfrom analytics developers 214 for publication. At 6416, healthinformation processing system 202 evaluates the applications, and ifapproved, places the application in the marketplace. At 6418, healthinformation processing system 202 allows patient 208 to download theapplication, and synchronize data with health information processingsystem 202 using device data upload selection element 1030 b.

The above description illustrates various embodiments of the presentinvention along with examples of how aspects of the present inventionmay be implemented. The above examples and embodiments should not bedeemed to be the only embodiments, and are presented to illustrate theflexibility and advantages of the present invention as defined by thefollowing claims. Based on the above disclosure and the followingclaims, other arrangements, embodiments, implementations and equivalentswill be evident to those skilled in the art and may be employed withoutdeparting from the spirit and scope of the invention as defined by theclaims.

What is claimed is:
 1. A computer-implemented method comprising:receiving, by a controller, a user request from a first system user of aplurality of system users for a communication of health data with ahealth information system, wherein the health information systemincludes the controller and a data store that stores health data relatedto the plurality of system users; determining, by the controller,whether the user request is a request for health data associated with asecond system user or a request for an analysis of health dataassociated with the first group of system users or a request tocommunicate health data; providing to the first system user, by thecontroller, health data stored by the second system user in the datastore based on access approval by the second system user in response tothe user request being a user request for health data associated withthe second system user; analyzing, by the controller, health data for afirst group of system users in response to the user request being arequest for an analysis of health data associated with the first groupof system users; providing, by the controller, to the first system userthe analyzed health data for the first group of system users; alteringmonitoring of health data of the patient based on the analyzed healthdata for the first group of system users indicating a request foradditional health data of a patient; altering treatment to the patientbased on the analyzed health data for the first group of system usersindicating a change to treatment to the patient; and communicating, bythe controller, health data associated with the first system user to asecond group of system users in response to the user request being arequest to communicate health data and the first system user hasdesignated the system users of the second group of system users.
 2. Themethod of claim 1, wherein the plurality of system users includes aplurality of health care providers, a plurality of payers, a pluralityof patients, a plurality of health data source developers, and aplurality of health analytics developers.
 3. The method of claim 1further comprising: receiving first ranking for a third system user froma third group of system users; generating a first composite ranking ofthe third system user based on the rankings of the third system user. 4.The method of claim 3 further comprising: receiving second rankings forthe third system user from a fourth group of system users; generating asecond composite ranking of the third system user based on the secondrankings of the third system user; generating a second overall compositeranking of the third system user based on the first and second rankingsof the third system user; determining, for each of the first rankings,whether said each first ranking is to be adjusted based on data relatedto the corresponding system user of the third group of system users;adjusting the first rankings for each corresponding system user of thethird group of system users for which an adjustment to said firstranking is determined; and adjusting the first overall composite rankingof the third system user based on the adjusted first rankings of thethird system user.
 5. The method of claim 1, wherein the first systemuser is a patient and the first user request is a download of healthdata from at least one heath data source of the patient at a selectedone of an automatic download or a patient initiated download.
 6. Themethod of claim 1, wherein the first system user is a health careprovider and the first user request is an upload of health data of apatient from the data store, the method further comprising selecting ahealth care application for use by the patient on a health data sourcebased on the uploaded health data.
 7. The method of claim 1 furthercomprising: determining, by the controller, from the health data of agroup of patients in the plurality of system users efficacy of at leastone of health data device used by the group of patients, healthapplications used by the group of patients, or medications taken by thegroup of patients; determining, by the controller, from the health dataof a group of patients in the plurality of system users trends in thehealth of said group of patients of at least one of health data device,health applications, or medications; and determining, by the controller,potential chronic health conditions in said group of patients based onsaid determined trends in the health of said group of patients.
 8. Themethod of claim 1 further comprising: receiving information for aplurality of health applications adding the information for theplurality of health applications to an online health application storefor access by system users that are patients.
 9. The method of claim 1further comprising: retrieving first health data for the patient;analyzing said first health data to generate a metric of health orwellness of said patient; retrieving second health data from a pluralityof health care sources associated with a plurality of patients andexecuting a health care application; and analyzing said second healthdata to evaluate the health care application.
 10. Thecomputer-implemented method of claim 1 further comprising: displaying,by the controller, a plurality of health data device icons, each healthdata device icons associated with a health data device used by apatient, wherein the data store further stores health data related tothe patient; displaying a plurality of health application icons, eachhealth application icon associated with a health application used by thepatient; associating each health data device with any healthapplications used by the patient; and displaying, for each health datadevice, a connection with each associated health application.
 11. Thecomputer-implemented method of claim 1 further comprising receiving, bythe controller, a plurality of first rankings for a health system from aplurality of patients; receiving a plurality of second rankings for thehealth system from a plurality of providers; generating a compositepatient ranking for the health system based on the plurality of firstrankings; generating a composite provider ranking for the health systembased on the plurality of second rankings; and generating a compositeoverall provider ranking for the health system based on the plurality offirst rankings and the plurality of second rankings.
 12. The method ofclaim 11, wherein generating a composite patient ranking for the healthsystem from the plurality of first rankings includes, for each patient,adjusting the ranking based on usage of the health system by the patientand determining a weighting of the patient ranking, wherein generating acomposite provider ranking for the health system from the plurality ofsecond rankings includes, for each provider, adjusting the ranking basedon prescriptions of the health system by the provider and determining aweighting of the provider ranking.
 13. The computer-implemented methodof claim 1 further comprising: receiving, by the controller, a devicedeveloper request from a device developer for a communication with ahealth information system, wherein the data store further stores adevice development document for a health data device and a standardinterface specification; analyzing, by the controller, the devicedeveloper request; upon determining the device developer request is arequest for the standard interface specification, downloading thestandard interface specification to the device developer; upondetermining the device developer request is a request for uploading thedevice development document to the health information system, uploadingthe device development document to the health information system; andanalyzing the device development document to determine whether thedevice development document complies with the standard interfacespecification.
 14. The computer-implemented method of claim 1 furthercomprising: receiving, by the controller, a device developer requestfrom a device developer for a communication of device data with a healthinformation system, wherein the data store further stores the devicedata; analyzing, by the controller, the device developer request; upondetermining the device developer request is a data upload request,uploading the device data to the health information system; upondetermining the device developer request is a specification uploadrequest, uploading an interface specification of a health data device tothe health information system; receiving a request for the interfacespecification from a health applications developer; and upon authorizingthe health application developer, providing the interface specificationto the health application developer.
 15. The computer-implemented methodof claim 1 further comprising: displaying, by the controller, aplurality of health data item icons, each health data item iconsassociated with a health data item related to a patient, wherein thedata store further stores the health data items related to the patient;receiving a selection of at least one health data items from thepatient; displaying a list of system users; receiving, for each selectedhealth data item, a selection at least one system user; and authorizing,for each selected health data item, access to the associated health dataitem by the at least one selected system user for sharing the selectedhealth data item with the at least one selected system user.
 16. Themethod of claim 15, wherein the system users include members of amedical provider network, other patients having the same disease as thepatient, other patients using the same health application as thepatient, using the same health data device as the patient, or the samebundle of health application and health data deice as the patient. 17.The computer-implemented method of claim 1 further comprising:receiving, by the controller, a patient request from a patient for acommunication of health data with a health information system, whereinthe data store further stores health data related to the patient;analyzing, by the controller, the patient request; upon determining thepatient request is an upload request, uploading health data related tothe patient from patient input, a health data source or a healthapplication to the health information system; and upon determining thepatient request is an analysis request downloading analysis of healthdata related to the patient.
 18. The method of claim 17, furthercomprising: generating advertising based on the prioritization of healthissues of the patient in response to the patient request being aprioritization of health issues; generating advertising based on theprioritization of chronic health of the patient in response to thepatient request being a prioritization of chronic health; displaying atleast one health data device, at least one health application or abundle of at least one health data device and at least one healthapplication available to the patient based on the health data related tothe patient in response to the patient request being a marketplacerequest; displaying recommendations shared by the patient in response tothe patient request being a recommendation review request; anddisplaying in a single screenshot data from all health data devices andhealth applications used by the patient in response to the patientrequest being a consolidation request.
 19. The computer-implementedmethod of claim 1 further comprising: receiving, by the controller, aprovider request from a provider for a communication of health data withthe health information system, wherein the data store further storespatient health data related to a patient; analyzing, by the controller,the provider request; upon determining the provider request is aprescription request, communicating a prescription to the patient; andupon determining the provider request is an analysis request downloadinganalysis of health data related to the patient.
 20. Thecomputer-implemented method of claim 1 further comprising: receiving, bythe controller, a payer request from a payer for a communication ofhealth data with a health information system, wherein the data storefurther stores patient health data related to a patient and providerdata related to a provider; analyzing, by the controller, the payerrequest; upon determining the payer request is a provider request,downloading analysis of health data related to the provider; and upondetermining the payer request is a patient analysis request, downloadinganalysis of health data related to the patient.